Neil Horman [off-list ref] 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 ;-)
On Tue, Apr 02, 2013 at 11:06:28AM -0700, Junio C Hamano wrote:
Neil Horman [off-list ref] writes:
quoted
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
On Tue, Apr 02, 2013 at 03:06:51PM -0400, Neil Horman wrote:
On Tue, Apr 02, 2013 at 11:06:28AM -0700, Junio C Hamano wrote:
quoted
Neil Horman [off-list ref] writes:
quoted
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
--
Scratch that, after some digging I located the git-new-workdir script in the
contrib directory, which does what we're talking about here.
Thanks!
Neil
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html