Re: [PATCH, 4th version] git-branch: register where to merge from, when branching off a remote branch

From: Paolo Bonzini <paolo.bonzini@gmail.com>
Date: Mar 2, 2007, 11:15 UTC
Message-ID: <45E8076F.1050606@lu.unisi.ch>
In-Reply-To: <20070302103240.GA13217@coredump.intra.peff.net>

Show 5 quoted lines

> IOW, my point is that branching should write the information it _knows_
> into the config: branch X was branched from branch Y. It should be up to
> the programs to _use_ that information in a reasonable way. As it is
> now, this patch makes the decision about how to use the information at
> the time of branching, which seems to be the source of a lot of objects.

The problem is that this will pollute the configuration file a lot.  I'm starting to wonder if all this branch information really belongs in .git/config at all.

Paolo

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