From: Stephen Boyd <sboyd@quicinc.com>
To: <git@vger.kernel.org>
Subject: Re: [BUG/TEST 0/2] bugs with cherry-pick renames
Date: Mon, 4 Mar 2013 10:48:52 -0800 [thread overview]
Message-ID: <5134EC94.6010602@quicinc.com> (raw)
In-Reply-To: <1360643262-1472-1-git-send-email-sboyd@codeaurora.org>
On 02/11/13 20:27, Stephen Boyd wrote:
> 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(+)
>
Any comments? Anyone else running into these bugs?
prev parent reply other threads:[~2013-03-04 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 4:27 [BUG/TEST 0/2] bugs with cherry-pick renames Stephen Boyd
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 ` Stephen Boyd [this message]
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=5134EC94.6010602@quicinc.com \
--to=sboyd@quicinc.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).