From: Jakub Narebski <jnareb@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: Salikh Zakirov <salikh@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] Introduce .git/BRANCH to point to the current branch
Date: Tue, 04 Dec 2007 12:42:43 -0800 (PST) [thread overview]
Message-ID: <m34peyur8r.fsf@roke.D-201> (raw)
In-Reply-To: <vpqbq96jjrf.fsf@bauges.imag.fr>
Matthieu Moy <Matthieu.Moy@imag.fr> writes:
> Salikh Zakirov <salikh@gmail.com> writes:
>
> > This combination leads to the confusing user experience
> > if the branch changes independently of the working directory.
> > This can happen in following cases:
All those cases are cases of not recommended workflows.
Please search the archives for idea of BASE extension to index
(instead of your separate file under .git/refs), and why it is
not in current git.
BTW. how in your proposal would you detach HEAD?
> There's another thing that your proposal could change: navigating back
> in history without loosing track of the branch you're on.
>
> Currently, I can do:
>
> # Oh, what did this look like two commits ago?
> $ git checkout HEAD^^
> # Ah, OK, let's go back to the tip
> $ git checkout branch-name
> ^^^^^^^^^^^
> But I have to remember and re-type the branch name.
No, you don't have. You can use
$ git checkout ORIG_HEAD
or
$ git checkout HEAD@{1}
--
Jakub Narebski
ShadeHawk on #git
Poland
next prev parent reply other threads:[~2007-12-04 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 20:08 [RFC] Introduce .git/BRANCH to point to the current branch Salikh Zakirov
2007-12-04 20:19 ` Matthieu Moy
2007-12-04 20:42 ` Jakub Narebski [this message]
2007-12-04 20:46 ` Junio C Hamano
2007-12-04 21:32 ` Matthieu Moy
2007-12-04 21:48 ` Junio C Hamano
2007-12-04 22:04 ` [PATCH] git-checkout --push/--pop Nanako Shiraishi
2007-12-05 6:59 ` Junio C Hamano
2007-12-05 10:26 ` Matthieu Moy
2007-12-05 17:44 ` David Kågedal
2007-12-06 23:39 ` [RFC] Introduce .git/BRANCH to point to the current branch Robin Rosenberg
2007-12-04 21:57 ` Salikh Zakirov
2007-12-04 22:06 ` Junio C Hamano
2007-12-04 22:08 ` Jakub Narebski
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=m34peyur8r.fsf@roke.D-201 \
--to=jnareb@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=salikh@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.