4 Nov
2009
4 Nov
'09
2:57 p.m.
Guillaume Lazzara <z(a)lrde.epita.fr> writes:
---
milena/ChangeLog | 90 +++++++++++++++++++++++-----------------------
milena/sandbox/ChangeLog | 20 +++++-----
2 files changed, 55 insertions(+), 55 deletions(-)
FWIW, I think we don't really need to sort ChangeLog entries by date
when patches come from git-svn. This is a consequence of the 2-step
workflow of decentralized SCMs like Git: you commit first (possibly
several times), then you propagate your changes to the server. BTW, Git
gives (and records) two roles to handle this: the *author* is the person
who wrote the patch, while the *committer* is the one applying it to a
repository. Both are recorded in Git logs.
Leaving the entries in the order they have been propagated (instead of
sorting them by date) has an advantage: you can read the description of
patches in the order they have been recorded in the server.
Anyway, much of this pain should vanish when we'll automate ChangeLog
generation and pinning from Git logs.