Re: status feature

Hi Derek, >How often do you type the following cvs commands? > >cvs status | grep Status: >cvs status | grep Status: | grep -v Up-to-date One time...? In the script...? >I'd be more than happy to post my patch to this list if there's any >interest in it. It's about 300 lines in unidiff format,

status feature

How often do you type the following cvs commands? cvs status | grep Status: cvs status | grep Status: | grep -v Up-to-date I got tired of doing this after about a month of using cvs (which I like very much BTW) and made a few changes to src/status.c to allow me to do something li

Re: Cannot commit as root

>I think there might be a legitimate reason to commit files as root. I'm >in the middle of attempting to put my system configuration files (this >/etc/*) into CVS. These files are owned by root, managed by root, etc. >but I'd still like to have a root-only repository that will allow me to >make ch

Re: Cannot commit as root

Derek Scherger wrote: > I think there might be a legitimate reason to commit files as root. I'm > in the middle of attempting to put my system configuration files (this > /etc/*) into CVS. These files are owned by root, managed by root, etc. > but I'd still like to have a root-only repository tha

Re: Cannot commit as root

On Wednesday, April 5, Derek Scherger wrote: > > I think there might be a legitimate reason to commit files as root. I'm > in the middle of attempting to put my system configuration files (this > /etc/*) into CVS. These files are owned by root, managed by root, etc. > but I'd still like to have a

WinCVS: proper method of submitting diffs with new files?

I can't seem to get the right combination with the following scenario: 1) I only have read access to the repository. 2) I want to create a diff that will contain the new files along with diffs against the modified ones to email to the maintainer. I tried 'cvs diff -c -N', but new files

Re: Cannot commit as root

Gerhard Sittig wrote: > > On Tue, Apr 04, 2000 at 13:50 +0300, Marius Oancea wrote: > > Hello cvs expoerts, > > If I want to use cvs from my workstation ( and here I am root ) > > how can I commit then changes to the server? If I am a normal > > user ... no problem, but if I'm r

Re: "cvs release" wishlist

Noel L Yap wrote: > [EMAIL PROTECTED] on 04/05/2000 01:33:39 PM [Let's prevent mistakes] > This isn't a new definition, it's always been documented this way. > > Exactly which mistakes are you talking about? If it's the possibility of doing: > cvs edit file > # modify file > c

Re: "cvs release" wishlist

[EMAIL PROTECTED] on 04/05/2000 01:33:39 PM >I'm sure that myself and other people could adapt to this new definition, but I >still prefer the idea of a design that prevents as many mistakes as possible. This isn't a new definition, it's always been documented this way. Exactly which mistake

Re: "cvs release" wishlist

I'm sure that myself and other people could adapt to this new definition, but I still prefer the idea of a design that prevents as many mistakes as possible. It seems to me that many users of CVS use 'cvs watch' and family to enforce communication and as a substitute for reserved checkouts. I ha

val-tags file question...( merging two repositories )....

I looked in the cvs manual and was unable to find any info on the val-tags file. If I am merging two repositories would it be ok to just merge the val-tags file( removing any duplicates of course )? Thanks! donald

Re: Changing file type from binary to ascii

Mark Derricutt schrieb: > How would one go about changing a file from binary to ascii, but retaining > its status between versions? Unfortunately there seems to be no possibility of assigning the -kb flag only to specific revisions of a file. The Cederqvist manual (version 1.10) says in section