From: Hilco Wijbenga <hilco.wijbenga@gmail.com>
To: Phillip Susi <phill@thesusis.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Stephen Finucane" <stephen@that.guru>,
"Git Users" <git@vger.kernel.org>
Subject: Re: Feature request: provide a persistent IDs on a commit
Date: Thu, 21 Jul 2022 11:58:24 -0700 [thread overview]
Message-ID: <CAE1pOi1pS76iXU8j=A54wPGHC7qofxrPDAO4uyy0d6yMxeQwvw@mail.gmail.com> (raw)
In-Reply-To: <87a692e8vj.fsf@vps.thesusis.net>
On Thu, Jul 21, 2022 at 9:39 AM Phillip Susi <phill@thesusis.net> wrote:
> Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>
> > This has come up a bunch of times. I think that the thing git itself
> > should be doing is to lean into the same notion that we use for tracking
> > renames. I.e. we don't, we analyze history after-the-fact and spot the
> > renames for you.
>
> I've never been a big fan of that quality of git because it is
> inherently unreliable.
Indeed, which would be fine ... if there were a way to tell Git, "no
this is not a rename" or "hey, you missed this rename" but there
isn't.
Reading previous messages, it seems like the
after-the-fact-rename-heuristic makes the Git code simpler. That is a
perfectly valid argument for not supporting "explicit" renames but I
have seen several messages from which I inferred that rename handling
was deemed a "solved problem". And _that_, at least in my experience,
is definitely not the case.
next prev parent reply other threads:[~2022-07-21 18:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 17:18 Feature request: provide a persistent IDs on a commit Stephen Finucane
2022-07-18 17:35 ` Konstantin Ryabitsev
2022-07-18 19:04 ` Michal Suchánek
2022-07-19 10:57 ` Stephen Finucane
2022-07-18 21:24 ` Glen Choo
2022-07-20 19:21 ` Konstantin Ryabitsev
2022-07-20 19:30 ` Michal Suchánek
2022-07-20 22:10 ` Theodore Ts'o
2022-07-21 11:57 ` Han-Wen Nienhuys
2022-07-24 5:09 ` Elijah Newren
2022-07-18 18:50 ` Ævar Arnfjörð Bjarmason
2022-07-19 10:47 ` Stephen Finucane
2022-07-19 11:09 ` Ævar Arnfjörð Bjarmason
2022-07-19 11:57 ` Michal Suchánek
2022-07-29 12:11 ` Stephen Finucane
2022-07-29 12:40 ` Jason Pyeron
2022-07-21 16:18 ` Phillip Susi
2022-07-21 18:58 ` Hilco Wijbenga [this message]
2022-07-22 20:08 ` Philip Oakley
2022-07-22 20:36 ` Michal Suchánek
2022-07-22 22:46 ` Jacob Keller
2022-07-23 7:00 ` Michal Suchánek
2022-07-24 5:23 ` Elijah Newren
2022-07-24 8:54 ` Michal Suchánek
2022-07-25 21:47 ` Jacob Keller
2022-07-26 3:49 ` Elijah Newren
2022-07-26 8:43 ` Michal Suchánek
2022-07-24 5:10 ` Elijah Newren
2022-07-24 8:59 ` Michal Suchánek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE1pOi1pS76iXU8j=A54wPGHC7qofxrPDAO4uyy0d6yMxeQwvw@mail.gmail.com' \
--to=hilco.wijbenga@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=phill@thesusis.net \
--cc=stephen@that.guru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).