l10n: git.pot: v2.2.0 round 2 (1 updated)

Generate po/git.pot from v2.2.0-rc2-23-gca0107e for git v2.2.0 l10n
round 2.

Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
l10n: batch updates for one trivial change

In order to catch up with the release of Git 2.2.0 final, make a batch
l10n update for the new l10n change brought by commit d52adf1 (trailer:
display a trailer without its trailing newline).

Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
l10n: de.po: translate 2 new messages

Signed-off-by: Phillip Sz <phillip.szelat@gmail.com>
Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
l10n: de.po: translate 2 messages

Signed-off-by: Ralf Thielow <ralf.thielow@gmail.com>
l10n: remove a superfluous translation for push.c

Ralf reported that '--recurse-submodules' option in push.c should not be
translated [1].  Before his commit is merged, remove superfluous
translations for push.c.

[1] http://www.spinics.net/lists/git/msg241964.html

Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
Git 2.2.0-rc3

Signed-off-by: Junio C Hamano <gitster@pobox.com>
log_ref_write: use strbuf instead of hand-rolled malloc

Besides being fewer lines of code, a strbuf helps in a few
ways:

  1. It makes it much more obvious that the combination of
     malloc with a magic "100" followed by "sprintf" is not
     a buffer overflow (it is not currently, because that
     100 is accounting for 2 sha1s and some whitespace, but
     it takes some careful reading to realize it).

  2. It makes it easier to write the logic of what is
     getting formatted. For example, in the existing code,
     we write a newline after the committer, and then
     sometimes overwrite that newline with the reflog
     message, only to add another newline. This is much
     easier written by adding the newline afterwards.

  3. It makes future patches to tweak the format much
     easier.
log_ref_write: optionally write refname into log

The usual reflog format does not contain the ref name, since
it is implicit in the location of the log. However, ...
read and write everything log