From: Junio C Hamano <gitster@pobox.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Git List" <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Trần Ngọc Quân" <vnwildman@gmail.com>
Subject: Re: Vietnamese l10n pull request problems
Date: Sun, 27 May 2012 22:23:15 -0700 [thread overview]
Message-ID: <7vr4u46fr0.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CANYiYbHWsfNSVESsZ6KoSH+_FEuLrrESC1_N0=DB5uMaWSv+Xg@mail.gmail.com> (Jiang Xin's message of "Mon, 28 May 2012 11:31:50 +0800")
Jiang Xin <worldhello.net@gmail.com> writes:
> Vnwildman, the new git l10n team leader for Vietnamese send me a huge
> pull request, it has some problems I think other l10n teams should care about.
>
> The URL for the pull request is https://github.com/git-l10n/git-po/pull/22 .
>
> 1. Commit log should has a signed-off-by line, no dought
There doesn't seem to have any S-o-b:. Please reject and kick this
series back to the team and ask them to redo their history.
> 2. Trival commits (from the same contributor, with not description in
> commit log) should be squashed or not, I am not sure.
As you noted in 3., there are too many useless merges directly from
me, and after remove them, there remain only commits with useless
single line subject "Continue translation into Vietnamese." (even
for a single-line log message that is wrong; omit the final
full-stop).
I think the reason why these have the same useless subject is
because they are separate only because the translator happened to
have stopped between commits, not because each of these is logically
separate and deserves a unique message.
They should all be squashed into a single commit, after removing the
merge in the wrong direction.
> 3. l10n team leaders should not merge git upstream directly.
Again, very true.
>>> Oh dear!I hate to change history!
That is not a valid excuse. The history leading to e4797a3bc277 will
never be in my tree, and if Jiang pulls it, the I won't be able to
pull from him either, so as far as wider upstream git is concerned,
the history did not even exist---there is no harm rebuilding a
history that never existed in the first place ;-)
Thanks.
next prev parent reply other threads:[~2012-05-28 5:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 3:31 Vietnamese l10n pull request problems Jiang Xin
2012-05-28 5:23 ` Junio C Hamano [this message]
[not found] ` <4fc320ce.04d8440a.0581.ffff8a98@mx.google.com>
2012-05-28 7:42 ` Jiang Xin
2012-05-28 8:36 ` Trần Ngọc Quân
2012-05-29 4:46 ` Jiang Xin
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=7vr4u46fr0.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=vnwildman@gmail.com \
--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).