From: Jon Seymour <jon.seymour@gmail.com>
To: Jeff King <peff@github.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] stash: fix false positive in the invalid ref test.
Date: Thu, 7 Apr 2011 08:47:07 +1000 [thread overview]
Message-ID: <BANLkTimqG4XSTRGH-+EMi6vYL7N8JU1Mtw@mail.gmail.com> (raw)
In-Reply-To: <20110406182726.GC8205@sigill.intra.peff.net>
On Thu, Apr 7, 2011 at 4:27 AM, Jeff King <peff@github.com> wrote:
> On Wed, Apr 06, 2011 at 09:21:13AM +1000, Jon Seymour wrote:
git stash drop
>
> Probably we should just squash your fix in with my first patch, and drop
> my test. Your fixed version is a superset of what mine tests.
>
I was wondering if it might be better to break up the original test,
so that each sub-function has its own invalid ref test? If there is
agreement, I can do this on top of 9355fc which is the tip of the
branch containing these fixes that has been merged into pu.
jon.
next prev parent reply other threads:[~2011-04-06 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 23:21 [PATCH] stash: fix false positive in the invalid ref test Jon Seymour
2011-04-06 18:27 ` Jeff King
2011-04-06 22:47 ` Jon Seymour [this message]
2011-04-06 23:04 ` Jeff King
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=BANLkTimqG4XSTRGH-+EMi6vYL7N8JU1Mtw@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@github.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).