From: Stefano Lattarini <stefano.lattarini@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
John Keeping <john@keeping.me.uk>,
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 3/6] transport-helper: clarify pushing without refspecs
Date: Thu, 18 Apr 2013 20:56:47 +0200 [thread overview]
Message-ID: <517041EF.5060000@gmail.com> (raw)
In-Reply-To: <1366243524-18202-4-git-send-email-felipe.contreras@gmail.com>
On 04/18/2013 02:05 AM, Felipe Contreras wrote:
> This has never worked, since it's inception the code simply skips all
>
s/it's/its/ (sorry for nitpicking)
> the refs, essentially telling fast-export to do nothing.
>
> Let's at least tell the user what's going on.
>
> [SNIP]
>
Regards,
Stefano
next prev parent reply other threads:[~2013-04-18 18:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 0:05 [PATCH 0/6] transport-helper: some clarifications and a fix Felipe Contreras
2013-04-18 0:05 ` [PATCH 1/6] transport-helper: clarify *:* refspec Felipe Contreras
2013-04-18 7:28 ` Thomas Rast
2013-04-18 8:18 ` Felipe Contreras
2013-04-18 12:39 ` Thomas Rast
2013-04-18 13:06 ` Felipe Contreras
2013-04-18 0:05 ` [PATCH 2/6] transport-helper: update refspec documentation Felipe Contreras
2013-04-18 0:05 ` [PATCH 3/6] transport-helper: clarify pushing without refspecs Felipe Contreras
2013-04-18 0:14 ` Sverre Rabbelier
2013-04-18 18:56 ` Stefano Lattarini [this message]
2013-04-18 0:05 ` [PATCH 4/6] transport-helper: warn when refspec is not used Felipe Contreras
2013-04-18 0:05 ` [PATCH 5/6] transport-helper: trivial code shuffle Felipe Contreras
2013-04-18 0:05 ` [PATCH 6/6] transport-helper: update remote helper namespace Felipe Contreras
2013-04-18 4:14 ` Felipe Contreras
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=517041EF.5060000@gmail.com \
--to=stefano.lattarini@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=florian.achleitner.2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--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 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).