Re: [vox-tech] CVS problem: .cvsignore is being ignored

2005-01-17 Thread Peter Jay Salzman
On Sun 16 Jan 05,  3:18 PM, Micah Cowan said:
 Peter Jay Salzman wrote:
 
 Hi all,
 
 I have a file:
 
   foo.tex
 
 in CVS.  I want to modify foo.tex on my local hard drive, but keep the
 repository copy as-is.  In other words, I don't want my changes to 
 foo.tex
 to be added to the repository version.
 
 If I place 'foo.tex' into .cvsignore (located in the root of my checkout
 directory), and do a general:
 
   cvs commit
 
 isn't foo.tex supposed to be ignored by the commit command?  I'm asking
 because it's not.   :)   Although 'foo.tex' is in .cvsignore, whenever I
 make changes to that file, cvs commit still wants to commit my changes.
 
 Using strace, I determined that CVS IS reading .cvsignore, and even reads
 foo.tex from that file.  Yet when I do a cvs commit, it still wants to
 update the repository copy of foo.tex with my local modified copy.
 
 Any ideas why?
 
 Pete
 
 If .cvsignore is only intended to keep files out of the repository that 
 are not already in it (this sounds possible),

This makes perfect sense to me.  Unfortunately, I found out it's not right.

.cvsignore honors update but does not honor commit, so it looks like we
have the worst of all possible worlds.

Perhaps there's a reason for this that I'm not thinking of, but if not,
let's hope the subversion people change this behavior.

Pete

-- 
The mathematics of physics has become ever more abstract, rather than more
complicated.  The mind of God appears to be abstract but not complicated.
He also appears to like group theory.  --  Tony Zee's Fearful Symmetry

GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E  70A9 A3B9 1945 67EA 951D
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] CVS problem: .cvsignore is being ignored

2005-01-17 Thread Ken Bloom
On Mon, 17 Jan 2005 10:50:06 -0500
[EMAIL PROTECTED] (Peter Jay Salzman) wrote:

 On Sun 16 Jan 05,  3:18 PM, Micah Cowan said:
  Peter Jay Salzman wrote:
  
  Hi all,
  
  I have a file:
  
foo.tex
  
  in CVS.  I want to modify foo.tex on my local hard drive, but keep
  the repository copy as-is.  In other words, I don't want my
  changes to  foo.tex
  to be added to the repository version.
  
  If I place 'foo.tex' into .cvsignore (located in the root of my
  checkout directory), and do a general:
  
cvs commit
  
  isn't foo.tex supposed to be ignored by the commit command?  I'm
  asking because it's not.   :)   Although 'foo.tex' is in
  .cvsignore, whenever I make changes to that file, cvs commit
  still wants to commit my changes.
  
  Using strace, I determined that CVS IS reading .cvsignore, and even
  reads foo.tex from that file.  Yet when I do a cvs commit, it
  still wants to update the repository copy of foo.tex with my local
  modified copy.
  
  Any ideas why?
  
  Pete
  
  If .cvsignore is only intended to keep files out of the repository
  that  are not already in it (this sounds possible),
 
 This makes perfect sense to me.  Unfortunately, I found out it's not
 right.
 
 .cvsignore honors update but does not honor commit, so it looks
 like we have the worst of all possible worlds.
 
 Perhaps there's a reason for this that I'm not thinking of, but if
 not, let's hope the subversion people change this behavior.

http://svnbook.red-bean.com/en/1.1/ch07s02.html explains that in
Subversion, the svn:ignore property (equivalent to CVS' .cvsignore file)
is used by svn add, svn status, and svn import.

-- 
I usually have a GPG digital signature included as an attachment.
See http://www.gnupg.org/ for info about these digital signatures.


pgphqKLtT4xFd.pgp
Description: PGP signature
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


[vox-tech] CVS problem: .cvsignore is being ignored

2005-01-16 Thread Peter Jay Salzman
Hi all,

I have a file:

   foo.tex

in CVS.  I want to modify foo.tex on my local hard drive, but keep the
repository copy as-is.  In other words, I don't want my changes to foo.tex
to be added to the repository version.

If I place 'foo.tex' into .cvsignore (located in the root of my checkout
directory), and do a general:

   cvs commit

isn't foo.tex supposed to be ignored by the commit command?  I'm asking
because it's not.   :)   Although 'foo.tex' is in .cvsignore, whenever I
make changes to that file, cvs commit still wants to commit my changes.

Using strace, I determined that CVS IS reading .cvsignore, and even reads
foo.tex from that file.  Yet when I do a cvs commit, it still wants to
update the repository copy of foo.tex with my local modified copy.

Any ideas why?

Pete

-- 
The mathematics of physics has become ever more abstract, rather than more
complicated.  The mind of God appears to be abstract but not complicated.
He also appears to like group theory.  --  Tony Zee's Fearful Symmetry

GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E  70A9 A3B9 1945 67EA 951D
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] CVS problem: .cvsignore is being ignored

2005-01-16 Thread Micah Cowan
Peter Jay Salzman wrote:
Hi all,
I have a file:
  foo.tex
in CVS.  I want to modify foo.tex on my local hard drive, but keep the
repository copy as-is.  In other words, I don't want my changes to foo.tex
to be added to the repository version.
If I place 'foo.tex' into .cvsignore (located in the root of my checkout
directory), and do a general:
  cvs commit
isn't foo.tex supposed to be ignored by the commit command?  I'm asking
because it's not.   :)   Although 'foo.tex' is in .cvsignore, whenever I
make changes to that file, cvs commit still wants to commit my changes.
Using strace, I determined that CVS IS reading .cvsignore, and even reads
foo.tex from that file.  Yet when I do a cvs commit, it still wants to
update the repository copy of foo.tex with my local modified copy.
Any ideas why?
Pete
 

Isn't that why it's called .cvsignore: so CVS will ignore it?  (jk)
If .cvsignore is only intended to keep files out of the repository that 
are not already in it (this sounds possible), then it may have been a 
design decision (or merely an accidental consequence of the algorithm 
used) to pay it no heed in the updating of existing repository entries, 
but only in the initial commitment of new entries. I'm sure the docs 
must cover this somewhere.

___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech