[Top][All Lists]

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

[Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.6.2-46-gb8f7ae

From: Ben Pfaff
Subject: [Pspp-commits] [SCM] GNU PSPP branch, master, updated. v1.6.2-46-gb8f7ae661
Date: Sat, 10 Sep 2022 23:54:29 -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  b92a77d2d1376d5bb7dbb9d012a099462293db16 (commit)
       via  b8f7ae6610f04de0b4325a905cc69beb65bad2ab (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 (b92a77d2d1376d5bb7dbb9d012a099462293db16)
             N -- N -- N (b8f7ae6610f04de0b4325a905cc69beb65bad2ab)

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 b8f7ae6610f04de0b4325a905cc69beb65bad2ab
Author: Ben Pfaff <>
Date:   Sat Sep 10 18:23:09 2022 -0700

    DEFINE: Improve error messages for parsing macro body.
    Without this change, errors always got reported following the macro body,
    not for the particular token at issue.


Summary of changes:
 src/libpspp/message.c | 3 +++
 1 file changed, 3 insertions(+)


reply via email to

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