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 "rsync".

The branch, master has been updated
  discards  8ded3833155396a07545d0863c9ea0d954a2695e (commit)
       via  dc6fb11b41daf37f1d47acde51b2a088e2892d0c (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 (8ded3833155396a07545d0863c9ea0d954a2695e)
            \
             N -- N -- N (dc6fb11b41daf37f1d47acde51b2a088e2892d0c)

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 -----------------------------------------------------------------
commit dc6fb11b41daf37f1d47acde51b2a088e2892d0c
Author: Wayne Davison <way...@samba.org>
Date:   Wed Jan 28 23:41:17 2009 -0800

    We only need to send --stats to a remote receiver now.

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

Summary of changes:


hooks/post-receive
--
rsync
_______________________________________________
rsync-cvs mailing list
rsync-cvs@lists.samba.org
https://lists.samba.org/mailman/listinfo/rsync-cvs

Reply via email to