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 rcsinfo to use the same commit message for ALL files to be
commi
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 [
...]
#
# Checks that the specified branches are valid for the given files.
# Branch may be "." for head.
#
###
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 rc
"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
[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 y
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
[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 directo
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
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
Fouts Christopher (6452) wrote:
> I just did a test commit and it prompted me per directory.
What connection method are you using? I use pserver .
--
Jim Hyslop
Senior Software Designer
Leitch Technology International Inc. (http://www.leitch.com)
Columnist, C/C++ Users Journal (http://www.cuj.co
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)
o: 'Fouts Christopher (6452)'; [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 pserver .
Actually, that is the dif
: 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, 2
-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 (current_parsed_root-
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->isr
-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 poi
wn template 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 ME
"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 wa
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 [
> ...]
[...perl program fragment elided...]
cvs only cares that
Thanks a lot for answering,
here are my answer:
* The version of cvs you are using.: > cvs-1.11.5
* The version of the host operating system you are using:
> Debian Linux:2.2.20-idepci
* The line of the commitinfo file that is calling your program
might help to determine if all the argu
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]
http://m
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 li
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
>
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
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::/cvsroot
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]
be shared? Thanks.
Howard
- Original Message -
From: "Laird Nelson" <[EMAIL PROTECTED]>
To: "Howard Zhou" <[EMAIL PROTECTED]>
Cc: "CVS Info" <[EMAIL PROTECTED]>
Sent: Wednesday, January 03, 2001 6:49 AM
Subject: Re: Does pre-commit script wi
Howard Zhou wrote:
>
> Yes, that's what I meant. I placed the pre-commit trigger script in
> commitinfo file but it doesn't run prior to editing cvs log with CVSROOT set
> to :ext: protocol. It works with CVSROOT set to a local dir or NFS
> mounting point.
When commitinfo scripts are run non-loc
ginal 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 l
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
"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 problem.
> - Original Message -
> From: "Derek R. Price" <[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 scr
#x27;s bad 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
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 t
tains 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
oc" 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 the exact file names
ut 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 Pr
ot;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 code ?? If anybody has the same problem or can gui
t; 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
39 matches
Mail list logo
