[Buildd-tools-devel] [GIT] schroot branch, master, updated. schroot-1.1.6-90-g18e487f

[Roger Leigh]

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

The branch, master has been updated
  discards  cce0235f49c15bb76e77092c0aa44431178a4d9c (commit)
  discards  586d55ed8d883e58298ecbe4d205a98280c76048 (commit)
  discards  e237e959d86a92172dd6b024817d71a99ce16dee (commit)
  discards  0e25ef5691f665d4bac7e43a50359fc5b915b2a8 (commit)
       via  18e487fe539ba47caf53c80b969316d67fa92b9b (commit)
       via  18fbe891e3ab5c3ef6a33d0a389729e875b0bb2c (commit)
       via  ea5b633f2d3a0665a0c626fbbe86b6f1b0aac426 (commit)
       via  b1430b886e30ecffc8f522a8c76140575feb26e8 (commit)
       via  855c8b0aa9bd227a44e07a978865faeecce7f6f2 (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 (cce0235f49c15bb76e77092c0aa44431178a4d9c)
            \
             N -- N -- N (18e487fe539ba47caf53c80b969316d67fa92b9b)

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 18e487fe539ba47caf53c80b969316d67fa92b9b
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 21 16:46:45 2009 +0000

    [setup] 05file: Use UNPACK_DIR and mount unpacked files
    
    In order to unify mounting/unmounting and session cleanup,
    05file unpacks into SCHROOT_UNPACK_DIR, which is then bind
    mounted onto SCHROOT_MOUNT_DIR.  This means it uses the same
    logic as all other chroot types, making the code simpler and
    more robust.

commit 18fbe891e3ab5c3ef6a33d0a389729e875b0bb2c
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 21 17:15:22 2009 +0000

    [build] Install SCHROOT_UNPACK_DIR

commit ea5b633f2d3a0665a0c626fbbe86b6f1b0aac426
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 21 16:43:51 2009 +0000

    [sbuild-session] Export SCHROOT_UNPACK_DIR for setup scripts

commit b1430b886e30ecffc8f522a8c76140575feb26e8
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 21 16:45:33 2009 +0000

    [build] Install SCHROOT_UNPACK_DIR

commit 855c8b0aa9bd227a44e07a978865faeecce7f6f2
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 21 16:44:29 2009 +0000

    [sbuild-session] Export SCHROOT_SESSION_ID in user environment

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

Summary of changes:
 AUTHORS |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
schroot