You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2005/06/20 05:00:42 UTC
Re: svn commit: r191362 - /spamassassin/trunk/build/README
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
actually, I'd prefer to keep it since 3.0.0 started -- there's a gzipped
"old" changelog in the distro which lists all changes up to 3.0.0,
so listing from 3.0.0 on in Changes keeps continuity.
- --j.
felicity@apache.org writes:
> Author: felicity
> Date: Sun Jun 19 13:16:32 2005
> New Revision: 191362
>
> URL: http://svn.apache.org/viewcvs?rev1362&view=rev
> Log:
> update build doc to point at when 3.1 development started, not 3.0...
>
> Modified:
> spamassassin/trunk/build/README
>
> Modified: spamassassin/trunk/build/README
> =============================================================================--- spamassassin/trunk/build/README (original)
> +++ spamassassin/trunk/build/README Sun Jun 19 13:16:32 2005
> @@ -72,10 +72,11 @@
>
> - For releases on the trunk (e.g. a .0 release):
>
> - TZ=UTC svn log -r HEAD:5810 --non-interactive > Changes
> + TZ=UTC svn log -r HEAD:46030 --non-interactive > Changes
>
> - r5810 was the start of the 3.0.0 (2.70 at the time) work; replace
> - with the correct rev number for the point you want to start at.
> + r46030 was the start of the 3.1.0 work (created 3.0 branch); replace
> + with the correct rev number for the point you want to start at
> + if different.
>
> - Check in the updated Changes file.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS
iD8DBQFCtjFaMJF5cimLx9ARAq+4AJ0UXtnhuxF5qKJQkoaU38U2EurrzQCaAwmD
VWlojUp8Wd5gat+rntvcI5s=
=Hj2C
-----END PGP SIGNATURE-----
Re: svn commit: r191362 - /spamassassin/trunk/build/README
Posted by Theo Van Dinter <fe...@apache.org>.
On Sun, Jun 19, 2005 at 08:00:42PM -0700, Justin Mason wrote:
> actually, I'd prefer to keep it since 3.0.0 started -- there's a gzipped
> "old" changelog in the distro which lists all changes up to 3.0.0,
> so listing from 3.0.0 on in Changes keeps continuity.
If we really want to do this we should move the 3.0 stuff to a different file.
Traditionally, our Changes file has been since the last stable branch was
created which would be changes since 3.0, not changes since 2.60.
--
Randomly Generated Tagline:
How does it change many dyslexics to take a bulb light?