Commit messages

10 views
Skip to first unread message

Sarah Mei

unread,
Aug 5, 2011, 10:17:12 AM8/5/11
to diaspo...@googlegroups.com
I'll be working on them this weekend, so if you have any comments (beyond what you've said in other threads) let me know today. Thanks!

Raphael Sofaer

unread,
Aug 5, 2011, 3:20:54 PM8/5/11
to diaspo...@googlegroups.com
I've disabled them until we make them less annoying.

Johnneylee Rollins

unread,
Aug 5, 2011, 3:35:40 PM8/5/11
to diaspo...@googlegroups.com
Hey Sarah,
here are some ideas that might be worth checking in to.

A daily digest that contains a list of files changed and the summary
of the changes using the +/- rewrite feedback.

Perhaps a link to each file changed, or at least links to each of the
commits that day. The more clever we can get about displaying as much
information as succinctly as possible seems to be a good avenue to
explore.

Change the subject line to something like "Daily commit digest:
<date>" and have each commit show the commiter's name and email so
people with problems that the commit may have caused can be cc'd to
hopefully grab their attention faster.

I forgot if diaspora has a CT environment running. Maybe we could
incorporate that into the email by showing perhaps the current state
of the project build at the end of the day. Maybe also for each commit
if that would help. I think that might help start conversations and
get failing builds fixed quickly by more community members.

Stick a line at the bottom of each digest reminding individuals to
post replies below the digest message.

~Johnneylee

Tom Scott

unread,
Aug 5, 2011, 3:42:43 PM8/5/11
to diaspo...@googlegroups.com
On Friday, August 5, 2011 at 3:35 PM, Johnneylee Rollins wrote:
Change the subject line to something like "Daily commit digest:
<date>" and have each commit show the commiter's name and email so
people with problems that the commit may have caused can be cc'd to
hopefully grab their attention faster.
I am all about this. Sounds like a great way to please both sides of this debate. I would be more inclined to read a daily digest of commits on my lunch break than each one separately, as I have to keep focused on my day job...as soon as I'm notified of a commit email (usually with Growl), I normally just delete it so it doesn't clutter up my client, as I'm usually pretty busy during real working hours. With a daily email, it would be even easier to figure out what's going on and contribute because we can see a series of commits which would form a "final product" patch.

-T
Reply all
Reply to author
Forward
0 new messages