guile-commits
[Top][All Lists]
Advanced

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

[Guile-commits] branch master updated (68eb519 -> fa4a229)


From: Daniel Llorens
Subject: [Guile-commits] branch master updated (68eb519 -> fa4a229)
Date: Wed, 23 Nov 2016 12:06:50 +0000 (UTC)

lloda pushed a change to branch master
in repository guile.

     omits  68eb519   Deprecate scm_from_contiguous_array
     omits  1744d72   Document new array functions, with provisional names
     omits  070bc57   New functions (array-for-each-cell, 
array-for-each-cell-in-order)
     omits  acd9d5d   New functions array-from, array-from*, array-amend!
       new  d1435ea   New functions array-from, array-from*, array-amend!
       new  7ef9d0a   New functions (array-for-each-cell, 
array-for-each-cell-in-order)
       new  0bd7562   Document new array functions, with provisional names
       new  fa4a229   Deprecate scm_from_contiguous_array

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (68eb519)
            \
             N -- N -- N   refs/heads/master (fa4a229)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omits" are not gone; other references still
refer to them.  Any revisions marked "discards" are gone forever.

The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.


Summary of changes:



reply via email to

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