Subject: Re: why you don't provide patches between releases for download?
From: Vlad Harchev (firstname.lastname@example.org)
Date: Mon Sep 18 2000 - 02:21:05 CDT
On Mon, 18 Sep 2000, sam th wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Mon, 18 Sep 2000, Martin Sevior wrote:
> > On Sun, 17 Sep 2000, Vlad Harchev wrote:
> > >
> > > I just downloaded all *.gz files again - my connection breaks very often so
> > > I don't think I would have been able to checkout abi from less than 10
> > > attempts (you can't resume cvs checkouts :( ).
> > >
> > > I still hope that you will provide patches - most mature open source projects
> > > provide them.
> > >
> > If we ask Sam nicely I think he will expand his script to produce
> > nightly gzipped diffs from the current CVS to the 0.7.11 release and put
> > them on his website. What do you think Sam? It probabally only an extra 5
> > lines or so...
> Consider me asked nicely. It was only an extra 4 lines, even. However, I
> did do one thing to make my life easier - I added a tag in the CVS
> repository for 0.7.11. The tag is called 'release-version-0-7-11' ('.' is
> not allowed in tag names). This tag is present in expat, wv and abi (and
> will be present in the other modules once I get some authentication issues
> worked out). So, from now on, we should create tags whenever we release a
> new version.
Thank you very much for this. It's nice that so much of comfort required so
few efforts from you.
> Remember, to learn about tags (or about the rest of CVS) read the book at
> http://cvsbook.red-bean.com. It's worth it.
Thanks for URL. But anyway, cvs doesn't allow to get patches between releases
unless you have a checked out tree. Probably RCS does, but it doesn't allow
> sam th
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.1 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> -----END PGP SIGNATURE-----
This archive was generated by hypermail 2b25 : Mon Sep 18 2000 - 02:32:31 CDT