RE: Help: Obtaining User Changes

2003-06-30 Thread Hill, Benjamin W
Thanks! I did a: cvs log -d 2003-07-01 | grep date changes.log ...and that produces: date: 2003/05/13 10:36:10; author: [USERID]; state: Exp; ...which shows activity percentile over date periods. The changelog: cvs log -d 2003-07-01 ...produces some decent info too! Cheers, Ben

RE: Help: Obtaining User Changes

2003-06-30 Thread Hill, Benjamin W
This has made me think... Are there any good tools that can generate HTML reports from CVS ChangeLogs? I'd be looking for something that generates in tabular form, a report that would list the updates to files, and activity percentile of authors. I know there is view CVS, but would it do this

Re: Help: Obtaining User Changes

2003-06-30 Thread Riechers, Matthew W
Hill, Benjamin W wrote: Is there a method in CVS is obtain changes to files for a particular user, over a particular time? I am using pserver to connect to a remote repository, and would like to find out what files have been edited over a particular time range. CVSps

Re: cvs commands in a script

2003-06-30 Thread Larry Jones
Vijay Kumar writes: How can we include cvs commands in a shesll or perl script - no interactive. Just do it. -Larry Jones You should see me when I lose in real life! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED]

RE: Info-cvs Digest, Vol 7, Issue 54

2003-06-30 Thread Luis Gonzalez
cvs annotate program | grep user_id Best regards ... -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Enviado el: Lunes 30 de Junio de 2003 13:06 Para: [EMAIL PROTECTED] Asunto: Info-cvs Digest, Vol 7, Issue 54 Send Info-cvs mailing list submissions to [EMAIL

Checkout files to the same working directory

2003-06-30 Thread Martyn Klassen
I'd like to be able to checkout files from different locations in the repository to the same working directory. I always get complaints that the repository locations are different when I try and check the second project out in the same location as the first project. I would have thought it

Branch Merging

2003-06-30 Thread Eric Fritz
Although I've been using CVS for several years I've never used branches. Well, I was posed with yet another opportunity where branching would fit and decided to finally take the plunge. Unfortunately, the results are a bit worrisome to me... here is the scenario: I've got file x.c which is

Re: Info-cvs Digest, Vol 7, Issue 54

2003-06-30 Thread Bogdan Serbanoiu
On Mon, 30 Jun 2003 [EMAIL PROTECTED] wrote: Send Info-cvs mailing list submissions to [EMAIL PROTECTED] To subscribe or unsubscribe via the World Wide Web, visit http://mail.gnu.org/mailman/listinfo/info-cvs or, via email, send a message with subject or body 'help' to

Re: acl for cvs try II

2003-06-30 Thread Corey Minyard
Edward Peschko wrote: On Sun, Jun 29, 2003 at 09:42:11PM -0500, Corey Minyard wrote: Have you looked at my patch, at http://home.attbi.com/~minyard/? It's been around for a while and is well tested, and implements full ACLs (per directory, per file, and per branch) within CVS, and has a lot

Re: Checkout files to the same working directory

2003-06-30 Thread Larry Jones
Martyn Klassen writes: I'd like to be able to checkout files from different locations in the repository to the same working directory. I always get complaints that the repository locations are different when I try and check the second project out in the same location as the first project.

Re: Checkout files to the same working directory

2003-06-30 Thread Eric Siegerman
On Mon, Jun 30, 2003 at 12:39:14PM -0400, Martyn Klassen wrote: I'd like to be able to checkout files from different locations in the repository to the same working directory. [...] I would have thought it would be relatively easy for the information about file location to be stored in the

Re: acl for cvs try II

2003-06-30 Thread Edward Peschko
#1 is key for me - I need something where I don't need to download a new client for everyone who wants to use ACL. #2 is pretty important too - I want something centralized, one file that I can check and see at a glance who has access to what. If #1 and #2 holds for your patch, then like