OK new try. This
- no longer requires 1/5 (i'll resend full series later when the
wanted behavior is found)
- shows either detached from or detached at. We could even do 4
commits from detached point XXX, like we do 5 commits ahead of
upstream. But I'm not sure if we should do that.
-
Duy Nguyen pclo...@gmail.com writes:
- # Not currently on any branch.
+ # Detached at $ONTO
Without the context, I don't think Detached alone says something to
the user. Detached HEAD at ... would IMHO be clearer and at least give
the user enough keywords to search the web/doc for an
On Mon, Mar 4, 2013 at 5:25 AM, Junio C Hamano gits...@pobox.com wrote:
When a remote ref or a tag is checked out, HEAD is automatically
detached. There is no user friendly way to find out what ref is
checked out in this case. This patch digs in reflog for this
information and shows Detached
Duy Nguyen pclo...@gmail.com writes:
Instead of punting to Currently not on any branch, would it help
to show the place you first detached at, so that the user can then
grab that commit object name and run
$ git log --oneline $that_commit..
or something?
$that_commit would be
When a remote ref or a tag is checked out, HEAD is automatically
detached. There is no user friendly way to find out what ref is
checked out in this case. This patch digs in reflog for this
information and shows Detached from origin/master or Detached from
v1.8.0 instead of Currently not on any
When a remote ref or a tag is checked out, HEAD is automatically
detached. There is no user friendly way to find out what ref is
checked out in this case. This patch digs in reflog for this
information and shows Detached from origin/master or Detached from
v1.8.0 instead of Currently not on
6 matches
Mail list logo
