From nobody Thu Jan 4 19:49:03 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T5cby3ys4z555yf for ; Thu, 4 Jan 2024 19:49:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5cby26HLz42wC for ; Thu, 4 Jan 2024 19:49:18 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-5542a7f1f3cso1112009a12.2 for ; Thu, 04 Jan 2024 11:49:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1704397755; x=1705002555; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=8PtUCy3lct6+AYYI8o+TTLrFaDQOmEu+2v6Cu7si/R4=; b=ZXLXfSNgddqGZ2YlN08qZ5Fp7w/+2zhk8iMURB+RBxlwbOK9xlSRczcl8y0ZmlXPX8 0fwgT0NIx1UhbU2MubVvmvAWa7trGxNd4VBdfkD5cF4mx5dIs+zlSjzP3zvDhAwqs2fO oeCPnE2hkP+8OnTS4OAl7s4EeO1PQ30Ox6s8xT5ChngfnJ0yxov96n5J9y3FWZE8p94z DPgBjrf6b0TXuLoIqHHyIli4S2ZFBebdY0sgMlgtOcEp94oRzy19GezpAUyvIugeSycd NthtykTN/xZfJCHAuRLEDwQVMJSN22RTbfYYGuVX+TleuMhwMoov5RE/WQypOVgpSE8h yR3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704397755; x=1705002555; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8PtUCy3lct6+AYYI8o+TTLrFaDQOmEu+2v6Cu7si/R4=; b=NfOkRQ34B2wGGIwwCzihFX0AgM6EOPRG2ZTYU3Vo/QZoA6x7fXgks76FxSLqTF1M77 xCkEfnVH3NJKecd80t57Uzzd7lC22+WQVChZjiqDrRgVf01T+i4GW91uqcYsJQVEOu1d oSejpzk8U05B4AFvhl7g4hFdAe5WNnRqeI4tPXMhfkjNJRfMYGp5OdU3ioqK+6ryFvcM 3v+821u5OZ7ldhMbNUtzTz9FNg2S1f6qTW1pyWK2yaqPKGQ6nF9WBdCAdoBAguwpiO2U 8VmQsDFPO0y4gpVlR5LjM5ktnkPYPzDRuwDtJ6gdrDcZs3sALA24ehCaDMh6p+5mCBHU JjqA== X-Gm-Message-State: AOJu0Yz93UHBzG7Y6Eotjxz/KIEzlFzqHWHiuD3IWpt9IwEV/9YgaTKX RXuVUGRajRwjNFuVBM47kG/QrDeRDlD2JPX2CZUGP6oZTJGbsQ== X-Google-Smtp-Source: AGHT+IEcenbv/Q7mhjK05wtwUAoWzw+RyphZ+8eNLACWXbKg0Ac2SxCY7CeBb8vkp4qZPH2cK4pSiw5v6EGNFTR+Bng= X-Received: by 2002:a17:907:7625:b0:a28:a9a7:7b67 with SMTP id jy5-20020a170907762500b00a28a9a77b67mr435141ejc.53.1704397755266; Thu, 04 Jan 2024 11:49:15 -0800 (PST) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> In-Reply-To: <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> From: Warner Losh Date: Thu, 4 Jan 2024 12:49:03 -0700 Message-ID: Subject: Re: git repo port issues? To: Jamie Landeg-Jones Cc: Tomoaki AOKI , Brooks Davis , Yuri , FreeBSD Current , Bakul Shah Content-Type: multipart/alternative; boundary="000000000000c2494a060e24065b" X-Rspamd-Queue-Id: 4T5cby26HLz42wC X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] --000000000000c2494a060e24065b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jan 4, 2024, 12:14=E2=80=AFPM Jamie Landeg-Jones wrote: > Tomoaki AOKI wrote: > > > > > Or create database (key-value store would be sufficient) storing commit > > order (like r* of svn) and commit hash. > > I'm still not certain whether commit order or commit hash should be the > > "key". Possibly store hash as the key fisrt and store assigned MONOTONI= C > > order as value, then, add the just-stored order as key and hash as > > value in another database would be neeed. If the database can contain 2 > > value for 1 key, it would be suitable for you to store the assigned > > time in UTC as "when it is committed to FreeBSD master repo". > > I do miss the incrementing "r" value - it's a nice immediate way to > tell which update is more recent. Actually, to me, that is more important > than the date - I've attempted to base my changes on the date due to the > absense of such a useful field. > See sys/conf/newvers.sh for the 'n' value we use in uname strings. It's a linear count of commits on the first-parent branch back to the start of the repo. Also, the dates usualy are first order correct and i use them for the stats i run. Though I've also just dropped tags on the first commit of each year too... Also be advised that the pre FreeBSD 8 or so tree still has some surprising artifacts in it. Warner Actually, I think I may implement such a thing on my local cgit repo. > > https://cgit.dyslexicfish.net/ports/latest/tree/ > https://cgit.dyslexicfish.net/src/current/tree/ > > Cheers, Jamie > > --000000000000c2494a060e24065b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jan 4, 2024, 12:14=E2=80=AFPM Jamie Landeg-Jon= es <jamie@catflap.org> wrote= :
Tomoaki AOKI <junchoon@= dec.sakura.ne.jp> wrote:

>
> Or create database (key-value store would be sufficient) storing commi= t
> order (like r* of svn) and commit hash.
> I'm still not certain whether commit order or commit hash should b= e the
> "key". Possibly store hash as the key fisrt and store assign= ed MONOTONIC
> order as value, then, add the just-stored order as key and hash as
> value in another database would be neeed. If the database can contain = 2
> value for 1 key, it would be suitable for you to store the assigned > time in UTC as "when it is committed to FreeBSD master repo"= .

I do miss the incrementing "r" value - it's a nice immediate = way to
tell which update is more recent. Actually, to me, that is more important than the date - I've attempted to base my changes on the date due to th= e
absense of such a useful field.

See sys/conf/newvers.sh for the 'n' = value we use in uname strings.=C2=A0 It's a linear count of commits on = the first-parent branch back to the start of the repo.

Also, the dates usualy are first order corre= ct and i use them for the stats i run. Though I've also just dropped ta= gs on the first commit of each year too...

Also be advised that the pre FreeBSD 8 or so tree still = has some surprising artifacts in it.

Warner

Actually, I think I may implement such a thing on my local cgit repo.

https://cgit.dyslexicfish.net/ports/lates= t/tree/
https://cgit.dyslexicfish.net/src/current/= tree/

Cheers, Jamie

--000000000000c2494a060e24065b--