Hi Carsten,
o Carsten Bock on 02/09/2012 10:26 AM:
Module: sems
Branch: master
Commit: f57355e899a97d200d02759bd047368964b7ad0f
URL:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sems/?a=commit;h=f57355e899a97d200d02759bd047368964b7ad0f
Author: Carsten Bock<[email protected]>
Committer: Carsten Bock<[email protected]>
Date: Thu Feb 9 10:25:06 2012 +0100
Revert previous commit.
thanks.
and sorry for being picky: If possible, the first line of the commit
message should always be a summary of
- where the changes are done
(e.g.: sbc: bl_redis: ...), and
- what is changed, in a concise way
the reason is that the first line shows up in many lists, and it's
important to have the information when merging trees or cherry-picking
patches to maintain different version. If it's a bugfix, it should be
prefixed with 'b/f', if it's fixing another commit include the hash of
that one. reverts should possibly contain the hash of the reverted
commit ('previous' is not really precise with a dvcs).
thanks again!
Stefan
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
