Digest #166

[Marco Krohn]

Ok, thanks Danny!

Another feature wish:
* Sometimes I would like to add some context or a link to a commit
message. For example, the message "Added libalkimia to build system"
does not mention what "libalkimia" actually is (I have _not_ selected
the message for the CD). In these (few cases) I would like to add a
comment for our readers like "libalkimia is a library with common
classes and functionality used by finance applications for the KDE
SC".
* Also sometimes I would like to give a reason (for the CD team) why I
selected a specific commit message, e.g., I found the message "Someone
somewhere on the internet said this would crash, I had to prove him
wrong :-)" from David Faure quite funny.

The feature wishes are not high priority, though. I am now working on
reducing the backlog a bit ...

Have a great day,
  Marco

On Wed, Jan 26, 2011 at 12:56 PM, Danny Allen <danny at commit-digest.org> wrote:
> It could be difficult to get a good commit overview as I get less information from Git and its all decentralised, but i;ll investigate and see what I can come up with!
>
> Cheers,
> Danny
>
>
> ----- Original Message -----
> From: "Marco Krohn" <marco.krohn at googlemail.com>
> To: "digest" <digest at kde.org>
> Sent: Wednesday, 26 January, 2011 11:46:31 AM
> Subject: Re: Digest #166
>
> Yes, there are many commits now ... actually too many. I'll see what I
> can do about that ...
>
> By the way this also fixed part (1) as I see more interesting commits
> now. Do you think it is possible to link the messages to the commits
> such that we can see the details, i.e., which files were modified
> which code changed, again?
>
> Thanks and best regards,
>  Marco
>
> On Mon, Jan 24, 2011 at 6:14 PM, Danny Allen <danny at commit-digest.org> wrote:
>> Hi Marco,
>> 1) Yep, I knew this would happen: basically, with these decentralised Git repositories people feel more free to commit and also that their commits won't really be seen, so they tend to be less informative in the commit message. Also, Git allows people to work offline and push at a later date, so people commit more often and with less thought than they used to. Obviously this causes issues for us, i'll have to think about how to improve this...
>>
>> 2) You had filters set on your account (/kdevelop, /koffice, /kdelibs, /kdebase) so i've removed them for now, there should be commits to review now?! :)
>>
>> Cheers,
>> Danny
>>
>>
>> ----- Original Message -----
>> From: "Marco Krohn" <marco.krohn at googlemail.com>
>> To: "digest" <digest at kde.org>
>> Sent: Monday, 24 January, 2011 4:30:38 PM
>> Subject: Re: Digest #166
>>
>> On Mon, Jan 24, 2011 at 3:36 PM, Danny Allen <danny at commit-digest.org> wrote:
>>
>>> 1) Git commits were only recently introduced, and I noticed a sharp fall in SVN commits over this time as projects moved quickly to Git
>>
>> I noticed that git commit messages tend to be less informative and
>> interesting than svn commits. It this because a) we do not see all git
>> commits (because many of them happen locally) and the merge message is
>> not interesting or (b) developers do not care to comment their commits
>> (c) something else?
>>
>>> 2) Commits have only been reviewed in Enzyme up to 10th January - i'll try and send an email to inactive reviewers to get this to a more realtime activity. Also, if anyone here can help out, that'd be really welcome too!
>>
>> Interesting, I just double-checked: my review page is still empty...
>>
>> Have a nice day,
>>  Marco
>> _______________________________________________
>> Digest mailing list
>> Digest at kde.org
>> https://mail.kde.org/mailman/listinfo/digest
>>
> _______________________________________________
> Digest mailing list
> Digest at kde.org
> https://mail.kde.org/mailman/listinfo/digest
>