Re: Instructions concerning detached head lead to lost local changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Carl Worth <cworth@xxxxxxxxxx> writes:

> At this point, I _knew_ that I didn't care about the state I was
> leaving, (it was something random that I had done for testing). So I
> definitely didn't want to name it with option (2).
>
> I also knew I hadn't done any commits while detached, which is what I
> thought the warning was all about. So I wasn't worried about losing
> nothing with option (1).

Well, the wording could probably be improved because you _did_
care about the state you were leaving (the "state" is not just
what commit HEAD points at), but the suggestions did make it
sound as if your had to choose between only these two, and
neither would have worked for you.

> Can we fix this please?

The question is how.

We can admit that suggestions are just suggestions and listing
only two is more confusing than not saying anything concrete.

Alternatively we could add yet another suggestion that let's you
discard the detached HEAD but still keep your local changes.
Either --drop by Linus renamed to some sensible name, or "the
obscure but useful trick".

I dunno.

-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]