From: Marc Branchaud <marcnarc@xiplink.com>
To: coder5000@gmail.com
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2013, #02; Wed, 6)
Date: Thu, 07 Nov 2013 10:39:37 -0500 [thread overview]
Message-ID: <527BB439.8010606@xiplink.com> (raw)
In-Reply-To: <xmqq7gcl6pwi.fsf@gitster.dls.corp.google.com>
On 13-11-06 07:01 PM, Junio C Hamano wrote:
>
> There is a proposed rewording of advice message from "git push"
> patch, which is tentatively queued near the tip of 'pu' for now; it
> would be nice to get a few more sets of eyeballs. I am not sure if
> we should merge it before the 1.8.5 final, yet (we have i18n to
> worry about, among other things).
I was all set to comment (having been asked so nicely!), but the patch in pu
looks like the last "v3" version, of which there was some discussion[1] that
I believe should result in a v4. I prefer to hold off commenting until the
next update.
[1] http://thread.gmane.org/gmane.comp.version-control.git/235713/focus=237384
M.
prev parent reply other threads:[~2013-11-07 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 0:01 What's cooking in git.git (Nov 2013, #02; Wed, 6) Junio C Hamano
2013-11-07 15:39 ` Marc Branchaud [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=527BB439.8010606@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=coder5000@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).