Date: Wed, 7 Sep 2005 09:23:34 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Gordon Bergling <gbergling@0xfce3.net> Cc: freebsd-hackers@freebsd.org Subject: Re: how to handling read only cvs trees Message-ID: <20050907162334.GB19958@odin.ac.hmc.edu> In-Reply-To: <20050907133239.GA53278@node26.0xfce3.net> References: <20050907133239.GA53278@node26.0xfce3.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--GRPZ8SYKNexpdSJ7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Sep 07, 2005 at 03:32:39PM +0200, Gordon Bergling wrote:
> Hi,
>=20
> I currently working to get an old patch up to HEAD, but I have a problem
> with generating a diff from my work.
>=20
> I usually checkout out src from a local cvs mirror of the FreeBSD
> repository. I do this with
>=20
> cvs -Rd/home/ncvs checkout src
>=20
> Without the -R flag I must do the checkout as root to create a read
> lock.
>=20
> The changes are easly diff'ed with
>=20
> cvs -Rd/home/ncvs checkout -uN > ../path/to/release.{patch|diff}
>=20
> I added new files in existing directories with 'cvs add' so that
> these files are included in the generated patch.
>=20
> The problem I am faced with is that there are new directories with new
> files (a lot) and these files are not included in the patch. I tried to
> 'cvs add' the directories, but I am not allowed the create the
> directories in /home/ncvs. Sure I just could fire up sudo to do the
> work, but I am afraid that cvsup, which I use to mirror the cvs
> repository, could delete them with the next scheduled run.
>=20
> Has anyone a hint on how to handle this situation?
Either pack the files up in a shar or tarball or use diff -N against
/dev/null to create that part of the diff by hand. FWIW, CVS wouldn't
do it for you even if you could add the files.
-- Brooks
--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
--GRPZ8SYKNexpdSJ7
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFDHxQFXY6L6fI4GtQRAmSDAJ0drO/q7FZrWMPYsFTiuhGOPJp/JACguJze
ZWUsIwPeEFTLWOdecIoeG5o=
=PCVn
-----END PGP SIGNATURE-----
--GRPZ8SYKNexpdSJ7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050907162334.GB19958>