Given that we've now got 45 plugins and themes (w00t!) in extras and 6 branches, and the commit feed doesn't identify what files are being changed, it's been great when people clearly identify what's they're committed to in their commit messages. Could we try a standard approach? How about:
Plugin:LiveHelp my commit message Theme:Charcoal my commit message Branch:Atom my commit message
That way, we can assume things that aren't identified are to trunk, and easily see what else is going on.
> Given that we've now got 45 plugins and themes (w00t!) in extras and 6
> branches, and the commit feed doesn't identify what files are being
> changed, it's been great when people clearly identify what's they're
> committed to in their commit messages. Could we try a standard
> approach? How about:
> Plugin:LiveHelp my commit message
> Theme:Charcoal my commit message
> Branch:Atom my commit message
> That way, we can assume things that aren't identified are to trunk,
> and easily see what else is going on.
On Mar 31, 9:44 pm, "Michael C. Harris" <michael.twof...@gmail.com>
wrote:
> Given that we've now got 45 plugins and themes (w00t!) in extras and 6
> branches, and the commit feed doesn't identify what files are being
> changed, it's been great when people clearly identify what's they're
> committed to in their commit messages. Could we try a standard
> approach? How about:
> Plugin:LiveHelp my commit message
> Theme:Charcoal my commit message
> Branch:Atom my commit message
How about we just have the feed output append that info so that we
don't have to futz with it when we commit?
For the core repo mailing list, it already does this in the title.
On Mon, Mar 31, 2008 at 07:47:01PM -0700, ringmaster wrote:
> On Mar 31, 9:44 pm, "Michael C. Harris" <michael.twof...@gmail.com> > wrote: > > Given that we've now got 45 plugins and themes (w00t!) in extras and 6 > > branches, and the commit feed doesn't identify what files are being > > changed, it's been great when people clearly identify what's they're > > committed to in their commit messages. Could we try a standard > > approach? How about:
> > Plugin:LiveHelp my commit message > > Theme:Charcoal my commit message > > Branch:Atom my commit message
> How about we just have the feed output append that info so that we > don't have to futz with it when we commit?
> For the core repo mailing list, it already does this in the title.
Brilliant! Is that you volunteering to do such a thing?
