From: "Steven E. Harris" <seh@panix.com>
To: git@vger.kernel.org
Subject: Re: Dangerous "git am --abort" behavior
Date: Thu, 23 Dec 2010 17:06:14 -0500 [thread overview]
Message-ID: <m2tyi45ell.fsf@Spindle.sehlabs.com> (raw)
In-Reply-To: AANLkTikUn+Mco3YeJ7Rj=xZrr1H5xr1Z0=cknf1MdCqC@mail.gmail.com
Adam Monsen <haircut@gmail.com> writes:
> That's a good way to keep tabs on whether you're in the middle of a
> rebase or am (as well as many other statuses).
How so? How are you using it for this purpose?
--
Steven E. Harris
next prev parent reply other threads:[~2010-12-23 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 18:31 Dangerous "git am --abort" behavior Linus Torvalds
2010-12-20 19:35 ` Adam Monsen
2010-12-20 21:52 ` Drew Northup
2010-12-20 22:04 ` Adam Monsen
2010-12-23 22:06 ` Steven E. Harris [this message]
2010-12-23 22:32 ` Junio C Hamano
2010-12-24 0:24 ` Steven E. Harris
2010-12-21 0:30 ` Junio C Hamano
2010-12-21 18:29 ` Junio C Hamano
2010-12-21 18:46 ` Linus Torvalds
2010-12-21 18:47 ` Junio C Hamano
2010-12-22 9:49 ` Peter Krefting
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=m2tyi45ell.fsf@Spindle.sehlabs.com \
--to=seh@panix.com \
--cc=git@vger.kernel.org \
/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).