From: A Large Angry SCM <gitzilla@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: PJ Hyett <pjhyett@gmail.com>, Scott Chacon <schacon@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Nicolas Pitre <nico@fluxnic.net>, git list <git@vger.kernel.org>
Subject: Re: Git sideband hook output
Date: Fri, 11 Jun 2010 17:54:42 -0400 [thread overview]
Message-ID: <4C12B0A2.4020205@gmail.com> (raw)
In-Reply-To: <3B9F4351-4608-455E-B433-A5337A946F8A@wincent.com>
Wincent Colaiuta wrote:
> El 11/06/2010, a las 16:34, PJ Hyett escribió:
>
>> Hi,
>>
>>> On Thu, Jun 10, 2010 at 8:30 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
>>>> If its really a problem, maybe "remote: " prefix should turn into
>>>> something shorter and language agnostic, like "<< ". But thus far
>>>> we hadn't had to worry about it, since we didn't have translation
>>>> support in Git... (though yes, I see that is changing now).
>>>>
>> I'm also in favor of making the default '>>' instead of 'remote:' if
>> nothing isn't an option.
>
> Funny, as '>>' is basically meaningless. At least 'remote:' has semantic value (ie. it indicates _where_ something is coming from).
Seconded.
next prev parent reply other threads:[~2010-06-11 21:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 20:32 Git sideband hook output Scott Chacon
2010-06-08 21:46 ` Shawn O. Pearce
2010-06-09 8:04 ` Peter Kjellerstedt
2010-06-09 13:44 ` Nicolas Pitre
2010-06-10 12:56 ` Peter Kjellerstedt
2010-06-10 18:05 ` Nicolas Pitre
2010-06-10 18:30 ` Shawn O. Pearce
2010-06-10 18:49 ` Scott Chacon
2010-06-11 14:34 ` PJ Hyett
2010-06-11 14:45 ` Wincent Colaiuta
2010-06-11 15:11 ` Erik Faye-Lund
2010-06-11 23:52 ` Junio C Hamano
2010-06-12 4:07 ` Jeff King
2010-06-11 21:54 ` A Large Angry SCM [this message]
2010-06-11 15:18 ` Ævar Arnfjörð Bjarmason
2010-06-11 21:55 ` A Large Angry SCM
2010-06-09 6:10 ` Johannes Sixt
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=4C12B0A2.4020205@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
--cc=peter.kjellerstedt@axis.com \
--cc=pjhyett@gmail.com \
--cc=schacon@gmail.com \
--cc=spearce@spearce.org \
--cc=win@wincent.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.