From: Junio C Hamano <gitster@pobox.com>
To: Ralf Thielow <ralf.thielow@googlemail.com>
Cc: "Thomas Rast" <trast@inf.ethz.ch>,
"Pat Thoyts" <patthoyts@users.sourceforge.net>,
"Jiang Xin" <worldhello.net@gmail.com>,
"Thomas Rast" <trast@student.ethz.ch>, "Jan Krüger" <jk@jk.gs>,
"Christian Stimming" <stimming@tuhh.de>,
"Git List" <git@vger.kernel.org>
Subject: Re: Please review this pull request for maint branch with update of de.po
Date: Fri, 11 May 2012 15:28:11 -0700 [thread overview]
Message-ID: <7vr4uqjqtg.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAN0XMOJLrGcB3=jy09b57FPc=ZoRxmo1Gx09vOLoxPexEe5fiQ@mail.gmail.com> (Ralf Thielow's message of "Fri, 11 May 2012 21:50:41 +0200")
Ralf Thielow <ralf.thielow@googlemail.com> writes:
> On Fri, May 11, 2012 at 9:40 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Ralf Thielow <ralf.thielow@googlemail.com> writes:
>>
>>> What about a README file like "/po" has?
>>
>> Sorry, but I cannot tell what you want to know about it.
>
> This was just an idea to do it in the same way.
> What I want to say is that there is a README file in the po folder which
> telling people that if they want to change something here, they have
> to go through
> the git.l10n repo to get changes into the git-core repo.
> That's presumably the same situation here, isn't it?
Hmph. I thought we had something that was meant for contributors in
Documentation/SubmittingPatches, but apparently we don't.
prev parent reply other threads:[~2012-05-11 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANYiYbFf73hVen2sg1viNrXxt-g+tP=bF_ryBF8JYp0ZAL0b6A@mail.gmail.com>
2012-05-08 0:30 ` Please review this pull request for maint branch with update of de.po Jiang Xin
2012-05-08 2:24 ` Junio C Hamano
2012-05-08 7:32 ` Thomas Rast
2012-05-08 7:48 ` Ralf Thielow
2012-05-08 9:20 ` Jiang Xin
2012-05-11 19:21 ` Junio C Hamano
2012-05-11 19:37 ` Ralf Thielow
2012-05-11 19:40 ` Junio C Hamano
2012-05-11 19:50 ` Ralf Thielow
2012-05-11 22:28 ` Junio C Hamano [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=7vr4uqjqtg.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=patthoyts@users.sourceforge.net \
--cc=ralf.thielow@googlemail.com \
--cc=stimming@tuhh.de \
--cc=trast@inf.ethz.ch \
--cc=trast@student.ethz.ch \
--cc=worldhello.net@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).