On Tuesday 14 February 2006 21:10, you wrote: > 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). Why not allow something like git-checkout master~5 which implicitly does create a read-only branch "seek-point"? I do not think that it is important to remember the branch name you seek from. A branch could be marked readonly by above command with chmod a-w .git/refs/heads/seek And git-commit should refuse to commit on a readonly ref, telling the user to create a writable branch before with "git-branch new". This would also help "cg-seek" to prohibit the user to commit on "cg-seek-point" via "git-commit" (by setting cg-seek-point read-only). BTW, "origin" (and any local branch that tracks a remote one) should be set to readonly this way to signal that these are not developer branches. Josef - 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.htmlReceived on Wed Feb 15 08:32:49 2006
This archive was generated by hypermail 2.1.8 : 2006-02-15 08:33:00 EST