[Python-Dev] small commit emails nit

R. David Murray rdmurray at bitdance.com
Sun Mar 6 17:10:23 CET 2011


On Mon, 07 Mar 2011 01:11:24 +1000, Nick Coghlan <ncoghlan at gmail.com> wrote:
> On Mon, Mar 7, 2011 at 12:56 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> > On Mon, 7 Mar 2011 00:52:08 +1000
> > Nick Coghlan <ncoghlan at gmail.com> wrote:
> >>
> >> I'm actually OK with the status quo, but if we were going to change
> >> it, I would continue to leave (default) out.
> >>
> >> Completely unqualified =3D cpython default
> >> Only branch name =3D cpython branch
> >> Only repository name =3D other repository default
> >> repository name and branch name =3D other repository branch
> >
> > Well, I'm not sure, but the regularity of the "cpython" prefixes makes
> > it easier to distinguish cpython commits from non-cpython ones IMO.
> 
> It's a mental pattern matching thing - word layout is noticed before
> word content.

Um, yes, that's why having cpython in there makes it easier to recognize
cpython commits when scanning a list of subjects.

> So the suggested scheme:
> 
> [python-checkins] Lorem ipsum dolor sit amet
> [python-checkins] (3.1): Lorem ipsum dolor sit amet
> [python-checkins] devguide: Lorem ipsum dolor sit amet
> [python-checkins] devguide (hg_migration): Lorem ipsum dolor sit amet
> 
> provides more distinctive subject lines than the current:
> 
> [python-checkins] cpython: Lorem ipsum dolor sit amet
> [python-checkins] cpython (3.1): Lorem ipsum dolor sit amet
> [python-checkins] devguide: Lorem ipsum dolor sit amet
> [python-checkins] devguide (hg_migration): Lorem ipsum dolor sit amet
> 
> What we have isn't bad, but I agree with Benjamin that it could be better.

I don't feel strongly about it either way.

--
R. David Murray                                      www.bitdance.com


More information about the Python-Dev mailing list