git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Git List <git@vger.kernel.org>
Cc: Armin Kunaschik <megabreit@googlemail.com>,
	Eric Wong <normalperson@yhbt.net>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/3] minor fixes to some svn tests
Date: Fri, 13 May 2016 16:49:00 -0400	[thread overview]
Message-ID: <20160513204900.GA15433@sigill.intra.peff.net> (raw)
In-Reply-To: <20160513194716.GA9806@sigill.intra.peff.net>

On Fri, May 13, 2016 at 03:47:16PM -0400, Jeff King wrote:

> On Fri, May 13, 2016 at 02:23:25PM -0400, Jeff King wrote:
> 
> > This covers all cases detected by:
> > 
> >   git grep 'test -z [^"]'
> > 
> > (though note that has a few false positives for tests which
> > need an extra layer of quoting to do '\"').
> 
> I looked at those false positives, and they're really gratuitous uses
> of double-quotes that cause the extra layer of quoting.
> 
> So I set off to fix that, but along the way found an actual bug (in the
> final patch here), along with a few minor readability fixups.
> 
>   [1/3]: t/lib-git-svn: drop $remote_git_svn and $git_svn_id
>   [2/3]: t9100: enclose all test code in single-quotes
>   [3/3]: t9107: use "return 1" instead of "exit 1"

Note that I ended up rolling these into the series posted at:

  http://thread.gmane.org/gmane.comp.version-control.git/294539/focus=294577

Or <20160513204654.GA10684@sigill.intra.peff.net>, since I know Eric has
his own list archive. :)

-Peff

      parent reply	other threads:[~2016-05-13 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 19:47 [PATCH 0/3] minor fixes to some svn tests Jeff King
2016-05-13 19:48 ` [PATCH 1/3] t/lib-git-svn: drop $remote_git_svn and $git_svn_id Jeff King
2016-05-13 19:48 ` [PATCH 2/3] t9100: enclose all test code in single-quotes Jeff King
2016-05-13 19:50 ` [PATCH 3/3] t9107: use "return 1" instead of "exit 1" Jeff King
2016-05-13 20:49 ` Jeff King [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=20160513204900.GA15433@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=megabreit@googlemail.com \
    --cc=normalperson@yhbt.net \
    /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).