git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: RFC: allowing multiple parallel sequencers

From
Neil Horman <nhorman@tuxdriver.com>
Date
Apr 2, 2013, 19:06 UTC
Message-ID
<20130402190651.GA17620@hmsreliant.think-freely.org>
In-Reply-To
<7v38v8eriz.fsf@alter.siamese.dyndns.org>
On Tue, Apr 02, 2013 at 11:06:28AM -0700, Junio C Hamano wrote:
Show 13 quoted lines
> Neil Horman <nhorman@tuxdriver.com> writes:
> 
> > 	I've recently started looking into the possibility of having git support
> > multiple in-progress sequencers, and wanted to solicit opinions for how best to
> > do it.... The thoughts I had were:
> >
> > 1) A per branch sequence directory...
> > 2) Augment the git-stash command...
> 
> 3) A per branch working tree.
> 
> That is how I would do this myself, anyway ;-)
>

Not sure I completely follow. Are you suggesting that all untracked files, indexes and meta data in .git be saved during a branch switch?

Thanks Neil

Previous: Junio C HamanoNext: Neil Horman
Message 3 of 4 in “RFC: allowing multiple parallel sequencers”
  1. Neil HormanApr 2, 2013
  2. Junio C HamanoApr 2, 2013
  3. Neil HormanApr 2, 2013
  4. Neil HormanApr 3, 2013

Read the whole thread, see it on lore, or plain text.

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