2010/5/25 Piotr Jaroszyński <[email protected]>: >> I've enabled commit emails (sent to this list) for commits to any >> branch of gpxe.git and gpxe-staging.git. The emails use a >> significantly tweaked version of the default git commit email hook. > > Cool! Having done that it shouldn't be too hard to also send the > commits to CIA and get a CIA bot on #etherboot > I could look into it if you don't mind having the commit announced on > the channel.
That'd be great :-) >> I'm happy to modify this process in response to your comments, so >> please feel free to reply with any suggestions. Things we should >> probably consider: >> - Do we want a separate list for commit emails? (i.e., will YOU be >> annoyed if you get them on this list?) > > I would prefer so. Setting one up now. >> - Do we want commit emails for personal repositories? The Summer of >> Code students will be doing interesting work. > > I think sending them to CIA would be nice (maybe getting a separate > bot for #etherboot-gsoc if you don't want to see too much commit spam > on #etherboot :). Not sure about the mailing list. I think it'd be fine to send them to #etherboot, but maybe not to the mailing list. >> - Are there formatting changes that would make the emails easier to read? > > Setting From: to the commiter/author could be useful if someone > decides to respond. Or maybe just adding them to CC. The trouble is that you get one email per push of a branch, which may have multiple commits by multiple authors. I can have it Cc everyone involved, though. -- Josh _______________________________________________ gPXE-devel mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe-devel
