Re: Recording the current branch on each commit?

From: David Kastrup <dak@gnu.org>
Date: Apr 28, 2014, 06:07 UTC
Message-ID: <87zjj656my.fsf@fencepost.gnu.org>
In-Reply-To: <CALKQrgemFx=2JaC1BaRqCwEV+knC8QftxcZ7K0AsT9azzuyVdA@mail.gmail.com>

Johan Herland <johan@herland.net> writes:

> Obviously, the feature would necessarily have to be optional, simply
> because Git would have to keep understanding the old commit object
> format for a LONG time (probably indefinitely), and there's nothing
> you can do to prevent others from creating old-style commit objects.

Personally, I am _strongly_ opposed. How I name and juggle my private branches is nobody else's business in a distributed version control system.

They are private.  My personal workflow.  Not part of a commit.

-- 
David Kastrup

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.