Date: Thu, 04 Jan 2024 19:14:19 +0000 From: Jamie Landeg-Jones <jamie@catflap.org> 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? Message-ID: <202401041914.404JEJCm083648@donotpassgo.dyslexicfish.net> In-Reply-To: <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp> References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <ZZWz-14AXfcSY2AD@spindle.one-eyed-alien.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> <ZZXui1gm0IIVoWca@spindle.one-eyed-alien.net> <20240104183539.cef54811b98fe53c5841edca@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Tomoaki AOKI <junchoon@dec.sakura.ne.jp> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202401041914.404JEJCm083648>