Re: What's cooking in git.git (topics)

From: Nicolas Pitre <nico@cam.org>
Date: Nov 26, 2007, 04:29 UTC
Message-ID: <alpine.LFD.0.99999.0711252324360.9605@xanadu.home>
In-Reply-To: <20071126041521.GA21120@fieldses.org>

On Mon, 26 Nov 2007, J. Bruce Fields wrote:

> I do find that trying to work on top of a constantly rebased branch is
> annoying no matter how I do it.  So I sometimes wonder if we shouldn't
> instead be finding ways to avoid the practice.

I don't think it can't be avoided in many cases. Some stuff gets rebased because it has to be refined before it is merged in a more stable and more "official" repository. Working on top of a rebased branch could be much easier if there was a dedicated command to perform the local rebase of one's work after a fetch, just like the pull command does a merge after a fetch, at which point both work flows would be almost equivalent wrt ease of use.

Nicolas

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