Don't write a log entry if there were no changes
authorKarl Hasselström <kha@treskal.com>
Sun, 21 Sep 2008 12:17:41 +0000 (14:17 +0200)
committerKarl Hasselström <kha@treskal.com>
Sun, 21 Sep 2008 12:19:07 +0000 (14:19 +0200)
commit67b01c133fea32df4041ef68cb6d6f4d8fa1189e
tree0d4ee2b7b1d0643cef697a00342e0e5435667c03
parent9690617a55cba571d0cb25ed846ef41942063020
Don't write a log entry if there were no changes

Some commands end up calling log_entry() without verifying that they
did in fact change anything. (One example of this is a conflicting
push, which will log two entries, everything else and the conflicting
push, with the "everything else" part being empty if there was only
one patch to push.) So before appending to the log, make sure that the
entry we're appending isn't a no-op.

Signed-off-by: Karl Hasselström <kha@treskal.com>
stgit/commands/reset.py
stgit/lib/log.py