From: Stephen Boyd <sboyd@codeaurora.org>
To: git@vger.kernel.org
Subject: [BUG/TEST 0/2] bugs with cherry-pick renames
Date: Mon, 11 Feb 2013 20:27:40 -0800 [thread overview]
Message-ID: <1360643262-1472-1-git-send-email-sboyd@codeaurora.org> (raw)
I ran into these bugs the other day and didn't have time to
investigate further. So I wrote test cases for them instead.
Stephen Boyd (2):
t3501: Expose bug with cherry-pick into dirty trees w/ renames
t3501: Expose addinfo_cache error message in cherry-pick
t/t3501-revert-cherry-pick.sh | 60 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 60 insertions(+)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next reply other threads:[~2013-02-12 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 4:27 Stephen Boyd [this message]
2013-02-12 4:27 ` [BUG/TEST 1/2] t3501: Expose bug with cherry-pick into dirty trees w/ renames Stephen Boyd
2013-02-12 4:27 ` [BUG/TEST 2/2] t3501: Expose addinfo_cache error message in cherry-pick Stephen Boyd
2013-03-04 18:48 ` [BUG/TEST 0/2] bugs with cherry-pick renames Stephen Boyd
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=1360643262-1472-1-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--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 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.