[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Getfem-commits] [getfem-commits] fix-valgrind-issues updated (830123b -
[Getfem-commits] [getfem-commits] fix-valgrind-issues updated (830123b -> f710f52)
Sat, 16 Sep 2017 05:39:18 -0400 (EDT)
logari81 pushed a change to branch fix-valgrind-issues.
discards 830123b add debugging questions/info (not to be pushed to master)
new f710f52 add few new assertions inside ga_tree
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 (830123b)
N -- N -- N refs/heads/fix-valgrind-issues (f710f52)
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.
Summary of changes:
src/getfem_generic_assembly.cc | 17 +++++------------
1 file changed, 5 insertions(+), 12 deletions(-)
- [Getfem-commits] [getfem-commits] fix-valgrind-issues updated (830123b -> f710f52),
Konstantinos Poulios <=