From: Thomas Rast <trast@inf.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>,
Pat Thoyts <patthoyts@users.sourceforge.net>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
"Ralf Thielow" <ralf.thielow@googlemail.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: Tue, 8 May 2012 09:32:20 +0200 [thread overview]
Message-ID: <87ipg75drv.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <7vtxzr1kbd.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 7 May 2012 19:24:38 -0700")
[+cc Pat]
Junio C Hamano <gitster@pobox.com> writes:
> - git-gui/ part of my tree is maintained without the rest of git.git/
> tree by Pat Thoyts, and an update needs to go through that tree. I
> cannot take a change directly to that part. Doing so would make
> it impossible to update git-gui/ project independently.
>
> Please redo your tree by having the originating author separate the
> git-gui part out, make sure everybody on the l10n team is happy with the
> result, and then throw me another pull request. Also arrange the git-gui
> patch to go through Pat.
I suspected something like this might happen, but proposed a
simultaneous change anyway. My bad. Ralf, can you split it or should I
resend?
But for next time, can there be another solution? It seems that this
process will make it very hard in general to keep the git-gui and core
git translations in sync.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-05-08 7:32 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 [this message]
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
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=87ipg75drv.fsf@thomas.inf.ethz.ch \
--to=trast@inf.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jk@jk.gs \
--cc=patthoyts@users.sourceforge.net \
--cc=ralf.thielow@googlemail.com \
--cc=stimming@tuhh.de \
--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).