sm-commit AT lists.ibiblio.org
Subject: Source Mage code commit list
List archive
Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c)
- From: Jeremy Blosser <jblosser-smgl AT firinn.org>
- To: sm-commit AT lists.ibiblio.org
- Subject: Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c)
- Date: Sat, 3 Feb 2007 19:35:55 -0600
On Feb 04, Thomas Orgis [thomas-forum AT orgis.org] wrote:
> I think it is better to make apparently proactive version number changes
> than to slip "just another small fix" into an already released version.
> That practice gives us bad checksums when upstream sources do small
> changes and keep version number constant.
No, I would never say we should change it without making it visible, but
PATCHLEVEL does this as well as VERSION. Admittedly we don't really have a
policy on how we handle versions for the things we write our own code for.
Maybe we should just make it explicit that PATCHLEVEL is for spell changes,
not code changes, and stick with minor version changes like this.
Attachment:
pgpGTOa8MHCAk.pgp
Description: PGP signature
-
[SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c),
Thomas Orgis, 02/03/2007
-
Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c),
Jeremy Blosser, 02/03/2007
-
Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c),
Thomas Orgis, 02/03/2007
- Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c), Jeremy Blosser, 02/03/2007
-
Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c),
Thomas Orgis, 02/03/2007
-
Re: [SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c),
Jeremy Blosser, 02/03/2007
Archive powered by MHonArc 2.6.24.