Jakub Narebski <jnareb@xxxxxxxxx> writes:
> Junio C Hamano <gitster@xxxxxxxxx> writes:
> ...
>> [On hold]
>>
>> * nd/dashless (Wed Nov 28 23:21:57 2007 +0700) 1 commit
>> - Move all dashed-form commands to libexecdir
>>
>> I think this is a sane thing to do in the longer term. Will be in
>> 'next' after v1.5.4. I think "leave porcelain on PATH" might be also a
>> good thing as a transition measure.
>
> We would have to change the paragraph in INSTALL about git wrapper
> (which would be no longer optional, or at least no longer optional in
> the sense that you can just delete/not install this file), and its
> conflict with (old) GNU Interactive Tools (the other 'git').
Thanks for noticing. Please send in a proposed patch to do so; then
we can park it near the tip of this topic, and nobody will forget.
>> [Stalled]
>>
>> * ns/checkout-push-pop (Wed Dec 5 07:04:06 2007 +0900) 1 commit
>> - git-checkout --push/--pop
>>
>> A reasonably cleanly written cute hack, and I do not see this breaking
>> the normal codepath, so I do not mind merging this as long as people
>> find it useful.
>
> That would be nice to have, although as somebody[*1*] said, you usualy
> know that you should have pushed branch into stack when you want to
> 'pop'. So it would be nice to have (if possible and easy to implement)
> also "git checkout --previous" or "git checkout -".
> ...
Perhaps. There are a few issues, though.
* When you were on 'master' and say "co -", you would want to come back
to the 'master' branch, whose tip may have advanced since you
switched away from (e.g. "git push . experiment:master"), and that is
a desired behaviour. When you switch away from a detached HEAD, what
would we record? The fact the head was detached and its commit, so
next "co -" would come back to that exact commit in a detached state?
Or "co -" is meant to say "I was distracted and was away but now
let's go back to my normal working state" and should refrain from
touching the previous branch information? I tend to think it would
be the latter.
* There are a few commands that are not "git checkout" but still
switches branches ("rebase that branch on this one" form of rebase
and "bisect"). Personally, I think bisect should stop using the
branch 'bisect' but instead work on detached HEAD in the longer run,
but what would we do about "rebase"?
> [*1*] I'm sorry for no attribution
I think this was Matthieu Moy, <vpqir3de8t6.fsf@xxxxxxxxxxxxxx>,
http://article.gmane.org/gmane.comp.version-control.git/67133
>> * jc/pathspec (Thu Sep 13 13:38:19 2007 -0700) 3 commits
>> . pathspec_can_match(): move it from builtin-ls-tree.c to tree.c
>
> What is the status of this thingy, by the way?
As the topic group header says, it is [Stalled].
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
