[dev] [commits] Horde-Support branch master updated. 521a02d79e8fdf65095044abd6a5d7e48c62e2ec

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Ben Klang <ben at alkaloid.net>:
>
>> On Feb 11, 2009, at 6:01 AM, Jan Schneider wrote:
>>
>>> Zitat von Michael M Slusarz <slusarz at horde.org>:
>>>
>>>>  Remove hash from subject (not very useful)
>>>
>>>>  Print commits from oldest -> newest
>>>
>>> Thanks :)
>>>
>>> How about sending separate messages for each commit in a push? This
>>> would also allow us to add the changed file names back to the
>>> subject.
>>
>> Is it possible to add a commit message for a push?  Some kind of
>> "overall" commit message that summarizes the cumulative changes in a
>> push. Obviously that would require the developers to take an extra
>> step but it could be useful.
>
> You can squash commits for a push:
> http://feedproxy.google.com/~r/git-ready/~3/VGszOb_D6zU/squashing-commits-with-rebase.html

Yeah - i use interactive rebasing (and lately, 'git add [-p|-i]) all  
the time before sending out commit messages.

We've already chatted on the list about the Subject line.  As for the  
file list, some people like it (e.g. Mike R) and some people find it  
very annoying (e.g. me).  I believe a workable compromise was to have  
a list of "submodules" (imp, kronolith, framework, etc.) that were  
affected on the subject line. See  
http://lists.horde.org/archives/dev/Week-of-Mon-20090202/023739.html

Now someone just needs to code it :)

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]