Date: Thu, 04 Jan 2024 00:27:17 +0100 From: Steffen Nurpmeso <steffen@sdaoden.eu> To: Bakul Shah <bakul@iitbombay.org> Cc: Brooks Davis <brooks@freebsd.org>, Jamie Landeg-Jones <jamie@catflap.org>, FreeBSD Current <freebsd-current@freebsd.org>, yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: <20240103232717.CAc7Sxai@steffen%sdaoden.eu> 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>
index | next in thread | previous in thread | raw e-mail
Bakul Shah wrote in <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org>: |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. On the other hand, if a project agrees, and for example locks the main branch, any merging or plain committing to it can enforce commit-amending including date-updates etc, as well as expanding $CVS and @# SCCS format strings (i think by then this discussion came up in the past, and Warner Losh rejected such a thing, if i recall correctly ... but may not). --End of <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240103232717.CAc7Sxai>