Re: several quick questions
- From
Petr Baudis <pasky@suse.cz>
- Date
- Feb 14, 2006, 20:27 UTC
- Message-ID
- <20060214202728.GE31278@pasky.or.cz>
- In-Reply-To
- <87fymlvgzv.wl%cworth@cworth.org>
Dear diary, on Tue, Feb 14, 2006 at 09:10:28PM CET, I got a letter where Carl Worth <cworth@cworth.org> said that...
Show 14 quoted lines
> That gives a very natural name, "seek", for the operation I'd like. > > How about "git seek" for doing the operations above, and using some > reserved branch name, (say "seek"). Then, git-bisect could easily be > built on that, and git-commit could respect the "seek" name and refuse > to commit to it, (could tell the user how to create the branch > necessary to commit from the current point). > > There could also be a "git seek reset" to return to the HEAD saved by > the first in a chain of "git seek" operations. > > That looks like I minor generalization of existing behavior in > git-bisect, but it would provide an operation that I would find > useful.
Well, this is exactly what cg-seek does (and it's one of pretty old Cogito commands) - it even has the same name. ;-) See my other mail in this thread.
It works by creating a new branch cg-seek-point and storing the seeked point there; if HEAD is already on the branch, it merely changes the seek point and resets the working tree appropriately. cg-seek without any arguments will then return to your original head, whose name was stored in .git/head-name.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Of the 3 great composers Mozart tells us what it's like to be human, Beethoven tells us what it's like to be Beethoven and Bach tells us what it's like to be the universe. -- Douglas Adams