[PATCH 2 of 2] patchbomb: add --no-intro option

Greg Ward greg at gerg.ca
Thu Mar 1 13:45:04 CST 2012


On 01 March 2012, Yann E. MORIN said:
> (Note: in the following, Mercurial = the project, while hg = the tool)
> 
> The problem is that the intro/no-intro policy centers (IMHO) a lot around
> Mercurial's use-case, while a lot of other projects may have a different
> policy of requiring introduction message (at least the project I maintain
> does highly favor introduction messages, and accepts single-patch with
> introduction, because it makes sense in some cases).

I should just clarify, BTW, that I would really like to have a
"--no-intro" option ... or maybe all I want is the configuration you
added in your first patch. Maybe that is sufficient. After all, the
variation is usually project-to-project, not patchbomb-to-patchbomb.

I wasn't thrilled with my implementation of --no-intro, but I sent it
anyways to see what kind of reaction I would get. Matt shot it down,
so I moved on to other stuff. If you can do a better --no-intro patch
than mine, great!

       Greg


More information about the Mercurial-devel mailing list