From nobody Thu Jan 4 19:14:19 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 4T5bqh2jlTz571Qt for ; Thu, 4 Jan 2024 19:14:24 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4T5bqh1YMHz3x0n; Thu, 4 Jan 2024 19:14:24 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; none X-Catflap-Envelope-From: Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 404JELll083649; Thu, 4 Jan 2024 19:14:21 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 404JEJCm083648; Thu, 4 Jan 2024 19:14:19 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> Date: Thu, 04 Jan 2024 19:14:19 +0000 Organization: Dyslexic Fish To: junchoon@dec.sakura.ne.jp, brooks@FreeBSD.org Cc: yuri@FreeBSD.org, jamie@catflap.org, freebsd-current@FreeBSD.org, bakul@iitbombay.org Subject: Re: git repo port issues? References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> In-Reply-To: <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> User-Agent: Heirloom mailx 12.4 7/29/08 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 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Thu, 04 Jan 2024 19:14:21 +0000 (GMT) X-Rspamd-Queue-Id: 4T5bqh1YMHz3x0n 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:20473, ipnet:2001:19f0:7400::/38, country:US] 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 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 the absense of such a useful field. 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