From: John Keeping <john@keeping.me.uk>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Sverre Rabbelier <srabbelier@gmail.com>, Max Horn <max@quendi.de>,
Jonathan Nieder <jrnieder@gmail.com>,
Florian Achleitner <florian.achleitner.2.6.31@gmail.com>
Subject: Re: [PATCH v2 1/6] transport-helper: clarify *:* refspec
Date: Thu, 18 Apr 2013 11:06:11 +0100 [thread overview]
Message-ID: <20130418100610.GV2278@serenity.lan> (raw)
In-Reply-To: <CAMP44s35tmmgNd-vJQnqG56avSPY2NOBR6iR7eNtpfemXsfPJA@mail.gmail.com>
On Thu, Apr 18, 2013 at 05:02:11AM -0500, Felipe Contreras wrote:
> On Thu, Apr 18, 2013 at 4:45 AM, John Keeping <john@keeping.me.uk> wrote:
> > In my copy of pu I don't see the text "It's mandatory for 'export'", it
> > just stops after "It is recommended that all importers providing the
> > 'import' capability use this". That paragraph also starts with "This
> > modifies the 'import' capability" making no mention of export.
>
> This is patch 1 of 6, keep going.
Ah, I see now. I had read all of the patches initially, but then
focused on this one for discussion.
The end result after this series does look good, but I find it slightly
strange to take a step backwards on the way.
next prev parent reply other threads:[~2013-04-18 10:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 4:14 [PATCH v2 0/6] transport-helper: some clarifications and a fix Felipe Contreras
2013-04-18 4:14 ` [PATCH v2 1/6] transport-helper: clarify *:* refspec Felipe Contreras
2013-04-18 8:24 ` John Keeping
2013-04-18 9:27 ` Felipe Contreras
2013-04-18 9:45 ` John Keeping
2013-04-18 10:02 ` Felipe Contreras
2013-04-18 10:06 ` John Keeping [this message]
2013-04-18 17:27 ` Junio C Hamano
2013-04-18 19:07 ` Felipe Contreras
2013-04-18 4:14 ` [PATCH v2 2/6] transport-helper: update refspec documentation Felipe Contreras
2013-04-18 4:14 ` [PATCH v2 3/6] transport-helper: clarify pushing without refspecs Felipe Contreras
2013-04-18 10:11 ` John Keeping
2013-04-18 10:14 ` Felipe Contreras
2013-04-18 10:24 ` John Keeping
2013-04-18 17:29 ` Junio C Hamano
2013-04-18 18:35 ` John Keeping
2013-04-18 17:28 ` Junio C Hamano
2013-04-19 0:27 ` Eric Sunshine
2013-04-19 0:30 ` Felipe Contreras
2013-04-19 3:41 ` Junio C Hamano
2013-04-18 4:14 ` [PATCH v2 4/6] transport-helper: warn when refspec is not used Felipe Contreras
2013-04-18 17:30 ` Junio C Hamano
2013-04-18 19:12 ` Felipe Contreras
2013-04-18 4:14 ` [PATCH v2 5/6] transport-helper: trivial code shuffle Felipe Contreras
2013-04-18 4:14 ` [PATCH v2 6/6] transport-helper: update remote helper namespace Felipe Contreras
2013-04-18 17:30 ` 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=20130418100610.GV2278@serenity.lan \
--to=john@keeping.me.uk \
--cc=felipe.contreras@gmail.com \
--cc=florian.achleitner.2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=max@quendi.de \
--cc=srabbelier@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 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.