Re: Semantics of change IDs (Re: Gerrit, GitButler, and Jujutsu projects collaborating on change-id commit footer)
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Apr 9, 2025, 19:14 UTC
- Message-ID
- <CAPig+cSN97oyYbF=mRijbgxUtED2q=u2PFAV+gPP3qM6Vm0OPg@mail.gmail.com>
- In-Reply-To
- <Z/a+AVopz+HLa1eL@ubby>
On Wed, Apr 9, 2025 at 2:51 PM Nico Williams <nico@cryptonector.com> wrote:
Show 10 quoted lines
> On Wed, Apr 09, 2025 at 11:02:41AM -0700, Junio C Hamano wrote: > > We designed not to etch such wrong renames/copoies in stone by > > recording them at the commit time. Instead we compare the before > > and after image to intuit the _intention_ of what the user wanted to > > do _when_ you _ask_ (i.e. when you run "git diff" or "git log"). > > Well, I suspect more likely that Linus didn't want to have some sort of > inode number nor some sort of explicit rename/copy indication as a > significant simplification that allowed Git to get shipped sooner. I'm > not questioning that nor trying to litigate rename/copy.
Contrary to your suspicion, what Junio describes above was a conscious and deliberate design decision by Linus[*].
[*]: https://lore.kernel.org/git/Pine.LNX.4.58.0504150753440.7211@ppc970.osdl.org/