pspp-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v2.0.0-pre2-5-gf4


From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v2.0.0-pre2-5-gf49d68c43
Date: Wed, 1 Nov 2023 22:58:42 -0400 (EDT)

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 "GNU PSPP".

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

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 f49d68c43b9c635f6dace47fe8193f8125c89206
Author: Ben Pfaff <blp@cs.stanford.edu>
Date:   Wed Nov 1 19:31:03 2023 -0700

    tests: Refine the last change.
    
    The remaining failures might be attributable to journal file creation
    errors.

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

Summary of changes:
 tests/ui/terminal/main.at | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
GNU PSPP



reply via email to

[Prev in Thread] Current Thread [Next in Thread]