From: Jeff King <peff@peff.net>
To: Thomas Gummerer <t.gummerer@gmail.com>
Cc: git@vger.kernel.org, sunshine@sunshineco.com,
Johannes.Schindelin@gmx.de, gitster@pobox.com
Subject: Re: [PATCH v3 0/4] git remote improvements
Date: Tue, 16 Feb 2016 10:52:23 -0500 [thread overview]
Message-ID: <20160216155223.GA918@sigill.intra.peff.net> (raw)
In-Reply-To: <1455616072-20838-1-git-send-email-t.gummerer@gmail.com>
On Tue, Feb 16, 2016 at 10:47:48AM +0100, Thomas Gummerer wrote:
> Previous rounds are at $gmane/286214 and $gmane/286278. Thanks to
> Peff and Eric for the reviews on the previous round.
This round looks good to me. Thanks for working on it!
Reviewed-by: Jeff King <peff@peff.net>
-Peff
next prev parent reply other threads:[~2016-02-16 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 22:39 [PATCH v2 0/4] git remote improvements Thomas Gummerer
2016-02-15 22:39 ` [PATCH v2 1/4] remote: use parse_config_key Thomas Gummerer
2016-02-15 23:04 ` Jeff King
2016-02-16 0:13 ` Thomas Gummerer
2016-02-15 22:39 ` [PATCH v2 2/4] remote: simplify remote_is_configured() Thomas Gummerer
2016-02-15 22:39 ` [PATCH v2 3/4] remote: actually check if remote exits Thomas Gummerer
2016-02-15 22:39 ` [PATCH v2 4/4] remote: use remote_is_configured() for add and rename Thomas Gummerer
2016-02-15 22:52 ` Eric Sunshine
2016-02-15 23:09 ` Jeff King
2016-02-16 0:16 ` Thomas Gummerer
2016-02-16 9:47 ` [PATCH v3 0/4] git remote improvements Thomas Gummerer
2016-02-16 9:47 ` [PATCH v3 1/4] remote: use parse_config_key Thomas Gummerer
2016-02-16 9:47 ` [PATCH v3 2/4] remote: simplify remote_is_configured() Thomas Gummerer
2016-02-16 9:47 ` [PATCH v3 3/4] remote: actually check if remote exits Thomas Gummerer
2016-02-16 9:47 ` [PATCH v3 4/4] remote: use remote_is_configured() for add and rename Thomas Gummerer
2016-02-16 15:52 ` Jeff King [this message]
2016-02-16 21:36 ` [PATCH v3 0/4] git remote improvements Junio C Hamano
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=20160216155223.GA918@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.com \
--cc=t.gummerer@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).