From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (May 2013, #04; Wed, 15)
Date: Tue, 28 May 2013 14:25:45 -0700 [thread overview]
Message-ID: <7vppwayexy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACsJy8Ct-ei7qbAW4qviQ6=q93ygxDcxRs9F3iHHV4-4Qz6qUA@mail.gmail.com> (Duy Nguyen's message of "Mon, 27 May 2013 17:36:46 +0700")
Duy Nguyen <pclouds@gmail.com> writes:
> Point taken. I guess the message would be something like this?
>
> Refname '%.*s' is ignored. It may be created by mistake.
>
> Or should we be more elaborate?
I dunno; with s/may be/may have been/, I think it is better than
"refname is ambiguous".
next prev parent reply other threads:[~2013-05-28 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 23:42 What's cooking in git.git (May 2013, #04; Wed, 15) Junio C Hamano
2013-05-16 0:25 ` David Aguilar
2013-05-20 10:18 ` Duy Nguyen
2013-05-20 16:17 ` Junio C Hamano
2013-05-21 7:13 ` Thomas Rast
2013-05-21 15:27 ` Junio C Hamano
2013-05-27 10:36 ` Duy Nguyen
2013-05-28 21:25 ` Junio C Hamano [this message]
2013-05-20 23:08 ` 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=7vppwayexy.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@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).