[Top][All Lists]

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

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.2.0-91-gabd1f8

From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.2.0-91-gabd1f81
Date: Tue, 1 Jan 2019 11:39:21 -0500 (EST)

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  f6ce01a9ab62ed38daf9c47e4b5dd8e52346beea (commit)
       via  abd1f816ca3b4f382bddf4564ad092aa934f0ccc (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 (f6ce01a9ab62ed38daf9c47e4b5dd8e52346beea)
             N -- N -- N (abd1f816ca3b4f382bddf4564ad092aa934f0ccc)

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 abd1f816ca3b4f382bddf4564ad092aa934f0ccc
Author: Ben Pfaff <address@hidden>
Date:   Tue Jan 1 08:36:05 2019 -0800

    pspp-dump-sav: Issue error message for too-large extension records.


Summary of changes:
 NEWS | 2 ++
 1 file changed, 2 insertions(+)


reply via email to

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