From: Junio C Hamano <junkio@cox.net>
To: Nicolas Pitre <nico@cam.org>
Cc: Theodore Tso <tytso@mit.edu>, Carl Worth <cworth@cworth.org>,
git@vger.kernel.org
Subject: Re: Instructions concerning detached head lead to lost local changes
Date: Thu, 01 Feb 2007 23:44:24 -0800 [thread overview]
Message-ID: <7vps8thulj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0702020206480.3021@xanadu.home> (Nicolas Pitre's message of "Fri, 02 Feb 2007 02:14:07 -0500 (EST)")
Nicolas Pitre <nico@cam.org> writes:
> It's just that moving around amongst thousands of commits to pin point a
> particular commit might require some digging work. This is why there
> might be some value in a particular position and why there is an attempt
> at protecting that "work".
>
> But since moving to another position while still remaining detached from
> any branch has the same potential for losing the important position and
> so without any kind of protection then it makes no sense to have such a
> protection when moving back to a branch.
Thanks -- I'd agree.
Also I agree that "reflog on HEAD" is the right direction as it
makes these 'protection' unnecessary. I've applied all your
patches from today on the topic, along with Johannes's "log -g
@{now}".
prev parent reply other threads:[~2007-02-02 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 22:51 Instructions concerning detached head lead to lost local changes Carl Worth
2007-02-01 23:49 ` Linus Torvalds
2007-02-02 1:41 ` Junio C Hamano
2007-02-02 2:00 ` Carl Worth
2007-02-02 2:06 ` Carl Worth
2007-02-02 2:49 ` Nicolas Pitre
2007-02-02 6:59 ` Theodore Tso
2007-02-02 7:14 ` Nicolas Pitre
2007-02-02 7:44 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vps8thulj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=nico@cam.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).