Date: Mon, 22 Jul 2013 09:00:28 +1000 From: John Marshall <john.marshall@riverwillow.com.au> To: Peter Wemm <peter@wemm.org> Cc: hubs@freebsd.org Subject: Re: FYI: Upcoming cvsup changes Message-ID: <51EC680C.10305@riverwillow.com.au> In-Reply-To: <CAGE5yCqbtGfFN_BGFjncD6%2BAhZ9knA8fL6cgorxmk=O-oopwaA@mail.gmail.com> References: <CAGE5yCqbtGfFN_BGFjncD6%2BAhZ9knA8fL6cgorxmk=O-oopwaA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2JEKOGGUEUCSGHJWFSWGU Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 22/07/2013 08:08, Peter Wemm wrote: > Right now, we have a rather fragile cvsup setup that's a bit painful > to deal with. >=20 > cvsup-master depends on a scan file for efficiency. So we have to > double-cvsup internally to generate the scan files. >=20 > It looks like this: Thanks a lot for this Peter. It's really helpful to know what's going on and what to expect. I really appreciate you taking the time to sketch out all of this for CVSup mirror operators. I think that what you are doing sounds eminently sensible. Hope all goes well in implementing your proposed changes. --=20 John Marshall ------enig2JEKOGGUEUCSGHJWFSWGU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iEYEARECAAYFAlHsaBUACgkQw/tAaKKahKK1QQCgi6AGAb9rqaq7e/TWuHTPcn/r w80AoI3lc3cTupyS7UP/MeFTDzhUfnW9 =3KDP -----END PGP SIGNATURE----- ------enig2JEKOGGUEUCSGHJWFSWGU--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51EC680C.10305>