[Debian-l10n-commits] dl10n branch master updated. 175433044d81c6b5091f9bbbaad2a5480becf919

[Nicolas FRANÇOIS]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "dl10n".

The branch, master has been updated
  discards  e1f3fbd761f7b79508d9ca72fd31c5bbed80b9da (commit)
  discards  49b68570e14d0b9ec1bdad2daf9e1bf134805c2f (commit)
  discards  6bec985c941510f30164c1d4ffd15624f1b453a8 (commit)
  discards  cf8300b062c84d427649bdfad578ef38974b5443 (commit)
  discards  bd32c95715bed8fa6c21e429762e897dcbd4dbeb (commit)
  discards  5e3f30e9f80c3db8ad1a423226e4807b44e3d54b (commit)
       via  175433044d81c6b5091f9bbbaad2a5480becf919 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (e1f3fbd761f7b79508d9ca72fd31c5bbed80b9da)
            \
             N -- N -- N (175433044d81c6b5091f9bbbaad2a5480becf919)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------

http://anonscm.debian.org/gitweb/?p=debian-l10n/dl10n.git;a=commitdiff;h=175433044d81c6b5091f9bbbaad2a5480becf919

commit 175433044d81c6b5091f9bbbaad2a5480becf919
Author: Nicolas François <nicolas.francois at centraliens.net>
Date:   Sun Jun 17 20:44:36 2012 +0200

    Fix typo

-----------------------------------------------------------------------

Summary of changes:
-----------------------------------------------------------------------


hooks/post-receive
-- 
dl10n