On Wed, Sep 10, 2014 at 12:02:09AM +0100, Thomas Adam wrote: > On Tue, Sep 09, 2014 at 11:46:02PM +0100, Michael Treibton wrote: > > Hi, > > > > is there a good way to ignore the mvwm emails sent here for the code > > changes? Do they need to get emailed out? they're quite large in size, > > and i could try and filter them but i worry i will miss other mvwm > > items on this list. > > Just filter by "mvwm.*branch updated" in whatever means suits how > you'd usually filter email. > > > instead can there be a separate list for mail of source-coding changes? > > I don't think Tibbs would like to manage this, and I certainly > wouldn't want to subscribe to yet another list, to be honest. > > > do other people here find these emails useful? > > So far you're the first person to mention this. I really would rather > we kept these emails, especially since this list already has a > tradition of sending out similar emails from CVS.
Well, maybe we could limit the context diff to ~50 lines to limit the size of the commit messages. > One of the nicer features in my eyes of the output as I'm formatting > it, compared to that of CVS is you can see the actual diffstat. > Granted this might be rather unweildy at times (especially in terms of > a merge commit), and hence I can always try and adapt that, but it > gives a better---more instant---peer-review process, outside of the > review process we already have (c.f. people sending patches before > submitting to git, etc., etc.) Good point. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
