On Aug 12, 2013 11:06 PM, "Duy Nguyen" wrote:
>
> On Mon, Aug 12, 2013 at 3:37 PM, David Jeske wrote:
> > Is there currently any way to say "hey, git, show me what commits are
> > dangling that might be lost in the reflog?"
>
> How do you define d
On Mon, Aug 12, 2013 at 10:24 AM, Junio C Hamano wrote:
> Don't we already do that?
>
> Warning: you are leaving N commits behind, not connected to
> any of your branches:
>
> ... list of commits to be lost ...
This only shows on checkout... not reset, not submodule-update, nor
an
On Mon, Aug 12, 2013 at 6:23 AM, Duy Nguyen wrote:
> That would annoy me as I often work on top of detached HEAD on purpose
> and only create a branch when I want to save something. If the warning
> is to be moved, it should warn at the next checkout.
Yes, you're absolutely right ...
My point ab
@Junio - to put the issue in the context of your previous comments on
the topic... way back when you made a comment about warnings during
commits to detached heads..
http://git.661346.n2.nabble.com/RFC-Detached-HEAD-reminder-on-commit-td834710.html#a834959
> If we _really_ don't want newbies to s
> Would the temporary branch created by checking out a random commit be
> automatically deleted when checking out another branch, or would it be
> garbage-collected at some
> point later?
Yes, as I stated in my example, the ephemeral branch created from
checking out a random commit would be aut
Has there ever been any any discussion of creating an ephemeral-branch
name mechanism, instead of using detached HEADs?
By ephemeral, I mean that a branch-name could be created which would
live only so long as it is the only named way to reach a ref or the
ref is in the working directory. Ephemera
6 matches
Mail list logo
