Code review comment for lp://staging/~rom1-chal/bzr-builder/reporting_conflict_from_merge

Le lundi 19 juillet 2010 à 19:27 +0000, Martin Pool a écrit :
> On 19 July 2010 18:43, Romain Chalumeau <email address hidden> wrote:
> > For a future feature, I was thinking about a report template in
> > a .bazaar directory for instance. If none is present, the standard error
> > is reported. If a template is present, it replaces the values for the
> > revisions in conflict.
> >
> > Keywords might be something like :
> > revfrom_no / revto_no, revfrom_author / revto_author, etc...
>
> I think this basic concept would be useful to have within bzr itself.
>
> > An option --email-report may exist to automatically to email the report
> > to the one launching the command and the concerned developers.
>
> I think we should have a post-merge-conflicts hook, which can be
> configured in a particular context to send mail to whoever.

Hi,

I really like the idea of post-merge-conflicts.
Would help a lot for reporting with an automation of continuous
merging.

Shall i open a blue print in bzr ?

--