aclocal.m4 and autom4te.cache in CVS
Why have aclocal.m4 and autom4te.cache been added to CVS? These are generated by the build so version controlling them only adds noise. Or am I missing something? Jeremy Henty
On Sun, Oct 12, 2008 at 09:43:26AM +0100, Jeremy Henty wrote:
Why have aclocal.m4 and autom4te.cache been added to CVS?
Just checked in CVS Web and also a clean CVS checkout, and don't see those files added.
Or am I missing something?
I hope. :-) -- Cheers Jorge.-
On Mon, Oct 13, 2008 at 09:17:37AM -0300, Jorge Arellano Cid wrote:
On Sun, Oct 12, 2008 at 09:43:26AM +0100, Jeremy Henty wrote:
Why have aclocal.m4 and autom4te.cache been added to CVS?
Just checked in CVS Web and also a clean CVS checkout, and don't see those files added.
Yes you're right, they're not in CVS/Entries . I've started managing my dillo development by tracking the CVS checkout in one git repository (the "remote") and developing in a cloned repository (the "local"). So the remote repository should stay pristine, but it didn't. Looks like I screwed up and ran autogen.sh in the remote at some point. Apologies for the noise. BTW, is anyone else using git like this? I thought I saw some patches on the list that looked git-generated. Regards, Jeremy Henty
On Mon, Oct 13, 2008 at 02:06:32PM +0100, Jeremy Henty wrote:
On Mon, Oct 13, 2008 at 09:17:37AM -0300, Jorge Arellano Cid wrote:
On Sun, Oct 12, 2008 at 09:43:26AM +0100, Jeremy Henty wrote:
Why have aclocal.m4 and autom4te.cache been added to CVS?
Just checked in CVS Web and also a clean CVS checkout, and don't see those files added.
Yes you're right, they're not in CVS/Entries . I've started managing my dillo development by tracking the CVS checkout in one git repository (the "remote") and developing in a cloned repository (the "local"). So the remote repository should stay pristine, but it didn't. Looks like I screwed up and ran autogen.sh in the remote at some point. Apologies for the noise.
BTW, is anyone else using git like this? I thought I saw some patches on the list that looked git-generated.
I'm using mercurial, which uses a similar patch format for exporting patches. Regards, Johannes
On Mon, Oct 13, 2008 at 04:19:59PM +0200, Johannes Hofmann wrote:
On Mon, Oct 13, 2008 at 02:06:32PM +0100, Jeremy Henty wrote:
BTW, is anyone else using git like this? I thought I saw some patches on the list that looked git-generated.
I'm using mercurial, which uses a similar patch format for exporting patches.
Ah, it was probably your patches I was thinking of. Jeremy
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeremy Henty wrote:
Yes you're right, they're not in CVS/Entries . I've started managing my dillo development by tracking the CVS checkout in one git repository (the "remote") and developing in a cloned repository (the "local"). So the remote repository should stay pristine, but it didn't. Looks like I screwed up and ran autogen.sh in the remote at some point. Apologies for the noise.
BTW, is anyone else using git like this? I thought I saw some patches on the list that looked git-generated. I am using bzr with a similar setup.
Justus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjzaCIACgkQoPmwNWhsaZYENgCfSNnEZutmw0RoUbS7u4W+6r1P 8woAnjIPqNcBtZ5tAIY3jm4wW6mRa17p =LtQk -----END PGP SIGNATURE-----
participants (4)
-
4winter＠informatik.uni-hamburg.de -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de -
onepoint＠starurchin.org