From: Junio C Hamano <gitster@pobox.com>
To: Nanako Shiraishi <nanako3@bluebottle.com>
Cc: Matthieu Moy <Matthieu.Moy@imag.fr>,
Salikh Zakirov <salikh@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] git-checkout --push/--pop
Date: Tue, 04 Dec 2007 22:59:56 -0800 [thread overview]
Message-ID: <7vprxl1v9v.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200712042204.lB4M4SVB002260@mi1.bluebottle.com> (Nanako Shiraishi's message of "Wed, 5 Dec 2007 07:04:06 +0900")
Nanako Shiraishi <nanako3@bluebottle.com> writes:
> This introduces a branch-stack mechanism to record branch switching in $GIT_DIR/BRANCH_STACK file. If you are switching to another branch and plan to come back to the original branch soon, add '--push' option to record your current branch.
> When you want to come back, 'git checkout --pop' will switch back to the branch recorded at the top of the stack, while popping it.
>
> Signed-off-by: しらいしななこ <nanako3@bluebottle.com>
Hmph, is this in response to my "I am not sympathtic to 'I have to
remember'"?
Funnily enough, I often find myself almost typing pushd/popd when
switching branches, so in that sense "git checkout" to switch branches
does have some similarity to the notion of pushing and popping.
Matthieu, is this something that forgetful people would find useful?
Having said that, I think there are other push/pop people wanted from
you. Hint, hint...
next prev parent reply other threads:[~2007-12-05 7:00 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
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 [this message]
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=7vprxl1v9v.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=nanako3@bluebottle.com \
--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 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).