git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Gwyneth Morgan <gwymor@tilde.club>
To: Bran Hagger <brhagger@microsoft.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	Emily Shaffer <nasamuffin@google.com>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: Improving support for name changes in git
Date: Wed, 26 Apr 2023 18:35:39 +0000	[thread overview]
Message-ID: <ZElux+kFcskXVL9Y@tilde.club> (raw)
In-Reply-To: <LV2PR21MB31334981E02BCA25792BAFFCCF939@LV2PR21MB3133.namprd21.prod.outlook.com>

On 2023-04-04 18:00:00+0000, Bran Hagger wrote:
> Has there been any further work done on supporting git name changes that I missed? Are there any existing files without git history that face similar issues?
> 
> [1] https://code.googlesource.com/git/summit/2020/+/main/notes.md
> [2] https://lore.kernel.org/git/20210103211849.2691287-1-sandals@crustytoothpaste.net/

There was another proposal posted by brian last year, using signing keys
the author controls instead of hashes:
https://lore.kernel.org/git/20220919145231.48245-1-sandals@crustytoothpaste.net/T/

A different VCS, Pijul, recently adopted a system that seems similar to
brian's proposal, and may provide some inspiration on the user
experience. I haven't seen documentation for it, but there are some
examples of commands here:
https://nest.pijul.com/pijul/pijul/discussions/706

      parent reply	other threads:[~2023-04-26 18:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 18:00 Improving support for name changes in git Bran Hagger
2023-04-06  1:59 ` Junio C Hamano
2023-04-26 18:35 ` Gwyneth Morgan [this message]

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=ZElux+kFcskXVL9Y@tilde.club \
    --to=gwymor@tilde.club \
    --cc=brhagger@microsoft.com \
    --cc=git@vger.kernel.org \
    --cc=nasamuffin@google.com \
    --cc=sandals@crustytoothpaste.net \
    /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).