From: Andreas Schwab <schwab@linux-m68k.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Philip Oakley" <philipoakley@iee.org>,
"Scott Chacon" <schacon@gmail.com>,
"git list" <git@vger.kernel.org>
Subject: Re: git-scm.com refresh
Date: Tue, 08 May 2012 19:46:46 +0200 [thread overview]
Message-ID: <m262c6h8ft.fsf@igel.home> (raw)
In-Reply-To: <7vlil2wr8k.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Tue, 08 May 2012 09:51:39 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> I encountered another example yesterday after sending the above message
> [*1*]. I was fixing one small bug, and had a commit that updates code and
> adds a test vector. It is a single commit on top of the current branch
> tip, which allegedly as a buggy code.
>
> Then I wanted to double check that the bug really existed before the fix.
>
> git checkout HEAD^
> git show @{-1} t/ | git apply
Alternative:
git checkout @{-1} t/
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-05-08 17:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 23:29 git-scm.com refresh Scott Chacon
2012-05-05 0:26 ` Jakub Narebski
2012-05-05 22:24 ` Scott Chacon
2012-05-05 23:20 ` Josh Juran
2012-05-05 1:31 ` Junio C Hamano
2012-05-05 16:47 ` Felipe Contreras
2012-05-05 22:38 ` Scott Chacon
2012-05-06 1:39 ` Junio C Hamano
2012-05-06 2:31 ` Felipe Contreras
2012-05-06 3:51 ` Scott Chacon
2012-05-06 8:33 ` Philip Oakley
2012-05-07 17:06 ` Junio C Hamano
2012-05-08 16:51 ` Junio C Hamano
2012-05-08 17:46 ` Andreas Schwab [this message]
2012-05-08 18:00 ` Junio C Hamano
2012-05-05 9:14 ` Andrew Sayers
2012-05-05 14:01 ` Felipe Contreras
2012-05-05 14:36 ` Philip Oakley
2012-05-06 0:08 ` Neal Kreitzinger
2012-05-06 5:10 ` Neal Kreitzinger
2012-05-06 11:04 ` Matthieu Moy
2012-05-06 13:36 ` Scott Chacon
2012-05-07 4:18 ` Christian Couder
2012-05-07 17:08 ` Ævar Arnfjörð Bjarmason
2012-05-07 15:08 ` A Large Angry SCM
2012-05-07 21:04 ` Matthieu Moy
2012-05-09 22:13 ` Heiko Voigt
2012-05-08 12:29 ` Antonio Ospite
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=m262c6h8ft.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.org \
--cc=schacon@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).