Send patches for new/outgoing changeset notifications (RFC)

[Mads Kiilerich]

Thomas Arendsen Hein wrote, On 10/26/2012 10:17 AM:
> Hi!
>
> The notifications about new or outgoing changesets sent to this list
> (and to the crew mailinglist for new changesets in crew) currently
> consist of a single mail with the summary of each change and a link
> to hgweb showing the full change.
>
> In a two different projects that switched to Mercurial I was asked,
> if I could provide patches, too, which I implemented this week. The
> patches are sent using the patchbomb extension and are in the same
> thread as the initial notification mail.
>
> An example for the result:
>
> dive4elements/flys at 4250: 8 new changesets:
> http://lists.wald.intevation.org/pipermail/dive4elements-commits/2012-October/000163.html
>    [PATCH 1 of 8] Convert GaugeOverviewInfoService into RiverInfoService:
>    http://lists.wald.intevation.org/pipermail/dive4elements-commits/2012-October/000164.html
>    [PATCH 2 of 8] Change Servlet config for RiverInfoService
>    http://lists.wald.intevation.org/pipermail/dive4elements-commits/2012-October/000165.html
>    ...
>
> Is there an interest to have the same for this list?
> Or is this only useful if there is a separate mailing list to not
> disturb the normal discussion happening here too much?

Discussion of the changesets would probably rarely happen but would be 
on-topic on -devel. Channelling all diffs through the mailing list would 
however be too noisy.

If there is interest then I suggest setting up a separate read-only 
-commit mailing list (or two) where reply-to is set to -devel.

/Mads

ps, slightly related: could the 'crew ... outgoing changesets' and 
'mercurial ... new changesets' use the same changeset order?