Re: FW: FW: How to tell Pre commit script the exact File Name containing Spaces?

so that Pre-commit script will get files surrounded by double quotes but I am not known to CVS code ?? If anybody has the same problem or can guide me where to start... Pick up a copy of cvs 1.12.x and look at putting UseNewInfoFmtStrings=yes in your CVSROOT/config file along with changes

Re: FW: FW: How to tell Pre commit script the exact File Name containing Spaces?

to the args. But my script is getting from CVS server is a b c not a b c That is why for I in $@ not helped me Let two files named as a and b c then CVS server send to my script is a b c not a b c ... I think I need to modify slightly in CVS code so that Pre-commit script will get

FW: How to tell Pre commit script the exact File Name containing Spaces?

spaces, I could not parse the exact file names! If a file name is DRN 106.doc I will get there DRN and 106.doc. I am parsing the file names in my pre commit scripts as for file in $@. And I get DRN first and then 106.doc, but I want DRN 106.doc? Is there any way to tell pre commit script

Re: FW: How to tell Pre commit script the exact File Name containing Spaces?

commit scripts as for file in $@. And I get DRN first and then 106.doc, but I want DRN 106.doc? Is there any way to tell pre commit script the exact file names with spaces? Am Using CVS 1.11.17 on LINUX ES 3. -- Best Regards Paras Jain

FW: FW: How to tell Pre commit script the exact File Name containing Spaces?

server is a b c not a b c That is why for I in $@ not helped me Let two files named as a and b c then CVS server send to my script is a b c not a b c ... I think I need to modify slightly in CVS code so that Pre-commit script will get files surrounded by double quotes but I am not known to CVS

Re: Commit script

Jim.Hyslop writes: We must have configured our server differently - we only get one prompt per checkin command, no matter how many files or directories are involved. There's no such configuration option. If you don't get a prompt for each directory, you've not running a standard CVS release.

RE: Commit script

[EMAIL PROTECTED] wrote: Jim.Hyslop writes: We must have configured our server differently - we only get one prompt per checkin command, no matter how many files or directories are involved. There's no such configuration option. If you don't get a prompt for each directory, you've

RE: Commit script

What is normal CVS and local CVS? I can probably guess but I'd rather not. -chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim.Hyslop Sent: Tuesday, March 23, 2004 10:03 AM To: [EMAIL PROTECTED] Subject: RE: Commit script [EMAIL PROTECTED] wrote

RE: Commit script

I just did a test commit and it prompted me per directory. -chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fouts Christopher (6452) Sent: Tuesday, March 23, 2004 11:21 AM To: [EMAIL PROTECTED] Subject: RE: Commit script What is normal CVS

RE: Commit script

Fouts Christopher (6452) wrote: I just did a test commit and it prompted me per directory. What connection method are you using? I use mumble pserver /mumble. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal

RE: Commit script

Local connection, ie, user and server are on the SAME machine. -chris -Original Message- From: Jim.Hyslop [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 12:03 PM To: 'Fouts Christopher (6452)'; [EMAIL PROTECTED] Subject: RE: Commit script Fouts Christopher (6452) wrote: I

Re: Commit script

)'; [EMAIL PROTECTED] Subject: RE: Commit script Fouts Christopher (6452) wrote: I just did a test commit and it prompted me per directory. What connection method are you using? I use mumble pserver /mumble. Actually, that is the difference. It is a design simplification/optimization that causes

RE: Commit script

: Re: Commit script -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fouts Christopher (6452) wrote: Local connection, ie, user and server are on the SAME machine. -chris -Original Message- From: Jim.Hyslop [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 12:03 PM To: 'Fouts

Re: Commit script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fouts Christopher (6452) wrote: How can I achive the yet another alternative where only one log message is prompted even on a LOCAL connection? Hack your client (Jim Hyslop already pointed out the correct location - at the `if

Re: Commit script

Derek Robert Price wrote: Fouts Christopher (6452) wrote: How can I achive the yet another alternative where only one log message is prompted even on a LOCAL connection? Hack your client (Jim Hyslop already pointed out the correct location - at the `if (current_parsed_root-isremote)'

Re: Commit script

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd Denniston wrote: Derek Robert Price wrote: Fouts Christopher (6452) wrote: How can I achive the yet another alternative where only one log message is prompted even on a LOCAL connection? Hack your client (Jim Hyslop already pointed out the

RE: Commit script

and scripts to validate user, bug number etc... -chris -Original Message- From: Derek Robert Price [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 23, 2004 2:50 PM To: Todd Denniston Cc: Fouts Christopher (6452); [EMAIL PROTECTED] Subject: Re: Commit script -BEGIN PGP SIGNED MESSAGE- Hash

Re: Commit script

Fouts Christopher (6452) wrote: The BEST solution yet - simple and effective! I tried this and it worked! Now for another question - where is the default commit template? Note I don't have the source files so I can't check yet. I'll download them later so I can browse them. I want to

Re: Commit script

On Mon, 22 Mar 2004, Fouts Christopher (6452) wrote: I'm playing CVS admin for my group. Currently during the commit process, one gets prompted for a commit edit message window for every file to be committed. This is of course impractical for a lot of files. How can I set up a script in

Re: Commit script

Fouts Christopher (6452) writes: I'm playing CVS admin for my group. Currently during the commit process, one gets prompted for a commit edit message window for every file to be committed. CVS prompts for each *directory*, not each file. If you're really seeing something else, it's due to

RE: Commit script

[EMAIL PROTECTED] wrote: Fouts Christopher (6452) writes: I'm playing CVS admin for my group. Currently during the commit process, one gets prompted for a commit edit message window for every file to be committed. CVS prompts for each *directory*, not each file. If you're really

Format for 1.11.10's contrib's loginfo, used by log_accum commit script?

I asked this question before and got pointed to the Cederqvist manual, which does *not* help at all. Please don't tell me to RTFM, the answer is not there. We are on CVS 1.11.5, moving to 1.11.10. We are using a really old version (1.11.1p) of the log_accum.pl and loginfo files. I would like

Re: a commit script

I am currently out of the office and unable to reply to your email. I will return to the office on Monday, March 17th, 2003. If this matter cannot wait, I can be reached via phone at (717) 579-6168. ___ Info-cvs mailing list [EMAIL PROTECTED]

Re: a commit script

Derkaoui [EMAIL PROTECTED] writes: Thanks a lot for answering, here are my answer: * The version of cvs you are using.: cvs-1.11.5 Good. I am not sure why you consider . to be a HEAD 'branch' as the default cvs sources do not have any patch to pass the branch on the command line, just

Re: a commit script

Mark D. Baushke writes: * The line of the commitinfo file that is calling your program might help to determine if all the arguments make sense. ALL /usr/local/src/cvsssupport/commit.branch ${USER} I don't understand why you don't just use $ENV{'USER'} inside your perl script to

Re: a commit script

Larry Jones [EMAIL PROTECTED] writes: Mark D. Baushke writes: * The line of the commitinfo file that is calling your program might help to determine if all the arguments make sense. ALL /usr/local/src/cvsssupport/commit.branch ${USER} I don't understand why you don't

a commit script

Hi, I hope somebody could help me with these: I am using a script to control commit , here it is ( only the part that i think cause the probleme): Usage: # commit.branch username repository files1 branch1 [file2 branch2 ...] # # Checks that the specified branches are valid for the given files.

Re: a commit script

Derkaoui [EMAIL PROTECTED] writes: Hi, I hope somebody could help me with these: I am using a script to control commit , here it is ( only the part that i think cause the probleme): Usage: # commit.branch username repository files1 branch1 [file2 branch2 ...] [...perl program

Re: Does pre-commit script with a remote server?

news. Howard - Original Message - From: "Derek R. Price" [EMAIL PROTECTED] To: "Howard Zhou" [EMAIL PROTECTED] Cc: "CVS Info" [EMAIL PROTECTED] Sent: Friday, January 12, 2001 7:29 AM Subject: Re: Does pre-commit script with a remote server? The o

Re: Does pre-commit script with a remote server?

rd Zhou" [EMAIL PROTECTED] Cc: "CVS Info" [EMAIL PROTECTED] Sent: Thursday, January 11, 2001 6:02 AM Subject: Re: Does pre-commit script with a remote server? Howard Zhou wrote: Now if I use :pserver: method, I still have the same problem. Is :pserver: using rsh too? Nope, but I didn

Re: Does pre-commit script with a remote server?

ot; [EMAIL PROTECTED] To: "Howard Zhou" [EMAIL PROTECTED] Cc: "CVS Info" [EMAIL PROTECTED] Sent: Thursday, January 11, 2001 6:02 AM Subject: Re: Does pre-commit script with a remote server? Howard Zhou wrote: Now if I use :pserver: method, I still have the same probl

Re: Does pre-commit script with a remote server?

Howard Zhou wrote: Now if I use :pserver: method, I still have the same problem. Is :pserver: using rsh too? Nope, but I didn't understand the rest of your question. As for the first question, I have three possible solutions: 1) Set the CVSEDITOR variable on all clients to a script which

Re: Does pre-commit script with a remote server?

Message - From: "Howard Zhou" [EMAIL PROTECTED] To: "CVS Info" [EMAIL PROTECTED] Sent: Wednesday, January 03, 2001 12:09 AM Subject: Does pre-commit script with a remote server? I am trying to write a pre-commit script to insert a change id to cvs log. The commitlog gen

Does pre-commit script with a remote server?

I am trying to write a pre-commit script to insert a change id to cvs log. The commitlog generates the change id while editlog inserts the change it to a temporary template file in /tmp dir. They all work fine if $CVSROOT is local to a client machine. However, if I set $CVSROOT to :ext:host

Re: Does pre-commit script with a remote server?

Howard Zhou wrote: I am trying to write a pre-commit script to insert a change id to cvs log. Precommit scripts can't affect the file being committed, if by "precommit" you mean "fired by the commitinfo admin file". Cheers, Laird -- W: [EMAIL PROTECTED] / P: [E