Since CVS already tracks the full history of the project, it seems simpler
to just tag CVS with each release/snapshot as it is made.
That way you can drop back to a previous one just by cvs updating to that
tag..
--Josh
At 11:30 on 06/08/2001 EDT, "Douglas J. Hunley" <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 07 June 2001 22:02, Martin babbled:
> > Hi,
> > I am in favor of keeping older snapshots.
> > It is easy that way to find when some bug was introduced without
> > reconstructing an older version with CVS.
> > Also it is easy that way to track where and when bochs and plex86 grew
> > out of eachother.
> > For example: I am now implementing the diskd feature (use two disk
> > images) which was build into bochs a few months ago. This uses features
> > in bochs bios 1.3. This bios is quite different from plex86 bios version
> > 1.3. Only 1.1 is the same for both.
> >
> > For the schedule of snapshots. I would say once a week or once a month.
> > Or once a week but only keep the once a month snapshots.
> > Greetings,
> > Martin
>
> the emu10k1 driver guys do something that might interest you. they keep diffs
> around for a while and only the last 2(?) full CVS snapshots. if you want to
> drop back, you just run the diffs through a reverse patch... saves a lot of
> space on their server... but still lets "us" do what we need to do
> - --
> Douglas J. Hunley (Linux User #174778)
> http://hunley.homeip.net/ http://linux.nf/
>
> Old programmers never die. They just branch to a new address.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iEYEARECAAYFAjsg75YACgkQOPP+k4ZeTm0dygCgisGPJm2A2Eb/WaqwKdywuafv
> TnkAmQH6/zVdA1yUfPpR8qodDOzmRFsl
> =i0mV
> -----END PGP SIGNATURE-----
>
