Date: Wed, 3 Jan 2024 23:32:27 +0000 From: Brooks Davis <brooks@freebsd.org> To: Bakul Shah <bakul@iitbombay.org> Cc: Jamie Landeg-Jones <jamie@catflap.org>, FreeBSD Current <freebsd-current@freebsd.org>, yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: <ZZXui1gm0IIVoWca@spindle.one-eyed-alien.net> In-Reply-To: <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <ZZWz-14AXfcSY2AD@spindle.one-eyed-alien.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 03, 2024 at 03:09:15PM -0800, Bakul Shah wrote: > On Jan 3, 2024, at 11:22???AM, Brooks Davis <brooks@freebsd.org> wrote: > > > > Nothing about dates is centralized in git, but some server side checks > > could be implemented on CommitDate. IMO we should require that > > CommitDate be >= the previous one and less than "now". > > Given that git commit objects form a DAG, I don't see how you can > impose linearity. Check each commit in a push to ensure that its CommitDate is newer than its first parent's CommitDate (you could check them all, but as a project we're mostly linear). Seems like a pretty trivial property to enforce. -- Brooks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZZXui1gm0IIVoWca>