[Geany-devel] GIT commit mails format

Frank Lanitz frank at xxxxx
Mon Oct 31 17:36:44 UTC 2011


On Mon, 31 Oct 2011 16:44:52 +0000
Nick Treleaven <nick.treleaven at btinternet.com> wrote:

> On 31/10/2011 15:07, Nick Treleaven wrote:
> > On 31/10/2011 13:57, Matthew Brush wrote:
> >>>>> I'm not sure we would see a flood on a merge, probably only one
> >>>>> commit saying 'merged gtkbuilder branch'? The gtkbuilder commits
> >>>>> should appear as they are committed, not on merge.
> >>>>>
> >>>>
> >>>> I think when you merge it makes all the commits onto the branch
> >>>> that was merged into also. At least this is what happened on the
> >>>> xfce-commits list when one of the devs merged several branches
> >>>> with a total of 800+ commits in them, each triggering a commit
> >>>> mail :)
> >
> > Ok, but ideally it would do as I described, like the github commit
> > list for the scintilla-update merge:
> >
> > https://github.com/geany/geany/commits
> 
> Anyway I think the problem of only showing the first commit of the
> push in the subject makes the commit mails harmful because changes
> can easily be missed. This problem seems more important than the
> potential flooding issue. In practice our branch merges likely
> wouldn't have 800 commits.

Agreed. 

Cheers, 
Frank 
-- 
http://frank.uvena.de/en/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/devel/attachments/20111031/6d609e46/attachment.pgp>


More information about the Devel mailing list