Re: Recording the current branch on each commit?

From: David Kastrup <dak@gnu.org>
Date: Apr 29, 2014, 10:37 UTC
Message-ID: <87a9b42zh8.fsf@fencepost.gnu.org>
In-Reply-To: <535f7c35cb5b1_7c7c10e32f019@nysa.notmuch>

Felipe Contreras <felipe.contreras@gmail.com> writes:

Show 6 quoted lines

> David Kastrup wrote:
>
>> The default behavior of "git push".
>
> This is a minor change that not many people would notice, and it has not
> actually happend. But fine, let's count it as one.

Shrug. Your diatribe is to a good part about the default behavior of "git pull". The "minor" change affects multiple branches in upstream, while your "important change" affects a single local branch.

With that sort of bias, it's easy to convince yourself of anything.

-- 
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.