Source Mage code commit list

[Jeremy Blosser <jblosser-smgl AT firinn.org>]

On May 30, Arwed von Merkatz [v.merkatz AT gmx.net] wrote:
> On Tue, May 30, 2006 at 02:28:06PM -0500, Jeremy Blosser wrote:
> > On May 30, Arwed von Merkatz [v.merkatz AT gmx.net] wrote:
> > > On Tue, May 30, 2006 at 01:45:05PM -0500, David Kowis wrote:
> > > [...]
> > > > New commits:
> > > > commit fa0a51d7ba07336d798741b08d535f1ac65b743e
> > > > Author: David Kowis <dkowis AT shlrm.org>
> > > > Commit: David Kowis <dkowis AT shlrm.org>
> > > > 
> > > >     Updated to BUILD API2
> > > > 
> > > > commit 0210d7a2b11c09cfe70f4e75e875980861c0f31a
> > > > Author: David Kowis <dkowis AT shlrm.org>
> > > > Commit: David Kowis <dkowis AT shlrm.org>
> > > > 
> > > >     Fixed MD5 anomaly and moved to SOURCE_HASH
> > > > 
> > > 
> > > It would be a good idea to prefix commit messages with the spellname,
> > > that way it's much easier to review stuff (or find it later for
> > > cherry-picking).
> > 
> > Is there something going on that's different from P4 that we could 
> > possibly
> > address at the script level?
> 
> Not sure what you're asking here. This prefixing is a good idea in all
> SCMs we currently use, I noticed that in p4 recently while
> cherry-picking.

I was just asking if you were already getting this from the p4 commits
somehow since the format is a bit different.  If it's just something you
are wanting to see added everywhere we can wait til we have picked an scm
and look at getting it added to the commit message automatically or
something.

Attachment: pgpJZQUFqylBi.pgp
Description: PGP signature