I have been meaning to get this back to Karl Fogel. This is what
we did:
===
RCS file: /system/cvsroot/buildsvc/src/cvs2cl.pl,v
retrieving revision 1.1
retrieving revision 1.2
diff -c -r1.1 -r1.2
*** buildsvc/src/cvs2cl.pl2002/05/21
Matt, thanks for your response.
> are you saying that they must be checked out to unix format,
> even on windows machines? then how does Visual Basic compile
> the source code, since it expects it in CRLF format?
Yes, that is what I am saying. We have a multi-platform build
environment here. T
> > I need to be able to provide the CVS server with a directive
> > that forces a merge using the cvswrappers functionality,
> > overriding CVS's default COPY behavior for files marked as '-kb'.
>
> That is not currently possible.
Can you please be more verbose? Also, I guess I don't understand
I need to be able to provide the CVS server with a directive
that forces a merge using the cvswrappers functionality,
overriding CVS's default COPY behavior for files marked as '-kb'.
Without adding complications of explaining our build process
suffice it to say there is a requirement that all sou
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Is there a new set of [html] docs for the latest cvs release? The latest I
can find are vintage 1.11.3. Thanks.
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
> mehul choube wrote:
> >> Does anyone know how to check out just 1 file (as opposed
> to a whole
> >> directory) in WinCVS, Eclipse, or some other client?
> >
> > cvs checkout cvsClient/client.c
>
> Sorry, I've been directed to find a gui client that allows
> this. Do you know of any?
WinCVS
> I think you mean CVS 1.11.1p1 and 1.11.2 -- there is no 1.12 yet.
Larry, any idea when you'll roll a new release?
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
> > > That is, cvsphil can't login from the console, from telnet,
> > > rlogin, etc. I think this is mainly done by setting his
> login shell to
> > > "/sbin/nologin" or the equivalent.
> >
> > You'll also need to configure cvsphil such that he can only
> log on with
> > a particular keypair. O
> > A chroot environment is only good at containing
> > what's inside it. It
> > does not prevent access to the chroot environment
> > from outside.
>
> I see. I guess it's obvious that the repository would
> have to be within the chroot'ed environment meaning
> that such an environment wouldn't
You want to create an entry for your script in loginfo-- it runs
right after commitinfo.
> -Original Message-
> From: David Anderson [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, December 07, 2002 3:40 PM
> To: [EMAIL PROTECTED]
> Subject: Running a program after 'cvs commit' has completed
> >> Is there a way to share a single source file across multiple
> >> directories in CVS, so that if it gets committed/merged in
> >> one directory the update registers in both locations? I know
> >> that VSS has this concept, and was wondering if CVS offers
> >> any sort of similar function
> Is there a way to share a single source file across multiple
> directories in CVS, so that if it gets committed/merged in
> one directory the update registers in both locations? I know
> that VSS has this concept, and was wondering if CVS offers
> any sort of similar functionality. I was th
> Of course, diffing "diff" output makes for an unreadable mess, so
> instead I run both diffs in two xterm windows with the same
> geometry, then flip back and forth between the windows a few
> times quickly, looking for the characters that flicker. Our
> visual systems are very good at spotting
> At 01:06 PM 9/3/2002, Douglas Finkle wrote:
> >Yes, you're right... you can use either of the two methods
> >mentioned, 'cvs status', or the Entries file. Still, both
> >of these methods are client side and their success depends
> >upon software (e.
Yes, you're right... you can use either of the two methods
mentioned, 'cvs status', or the Entries file. Still, both
of these methods are client side and their success depends
upon software (e.g. Perl) that may or may not be present on
client machines.
I've yet to see a good reason why a patch
> > Some time ago John Cavanaugh wrote a patch for commit.c,
> > but I don't think it was ever incorporated-- don't know why.
>
> As John himself noted, the patch is not ready for prime time
> -- it does
> not include documentation updates and it is not upward compatible. In
> addition, I haven
> >> >> What is the best way to lock a branch? Should I use
> >>
> >> >How about:
> >>
> >> >``Please don't commit to this branch until told otherwise, or you
> >> >will be fired on grounds of inability to follow instructions.''
> >>
> >> >Why work with people that require a piece of software
Have a look at ViewCVS... it's much the same idea, but w/ some
very cool features added on (e.g. graphical history, sorting, and
more); written in Python, and actively being developed.
http://viewcvs.sourceforge.net/index.html
-D
___
Info-cvs mailing
Check out http://coombs.anu.edu.au/ipfilter/. You can make your
server listen on _only_ the desired interface.
> I presume thats a no on a interface binding option.
> Atm I already have a chain in place. But, I would
> prefer the cvs-server process -not- to even listen on
> the second interf
> I previously did a cvs import of 'third party code'. I have
> been making changes to the code, and checking these into cvs.
> I have done another import of the 'third party code'. I was
> hoping that I could pick only the parts of this latest code
> that I wanted to merge in with my changes.
>> Environment: cvs 1.11.1p running on unix. Clients are mostly
>> wincvs1.13.7+
>>(in-house modifications to prevent password display on the
>> screen)
>> Huh?
> Huh what?
There's no need to use passwd... you should be using keys. The
passphrase does _not_ go in as p/o the CVSROOT definitio
> Environment: cvs 1.11.1p running on unix. Clients are mostly
> wincvs1.13.7+
> (in-house modifications to prevent password display on the
> screen)
Huh?
> plink for ssh connection.
Also, use Pageant on Windows. UNIX will require ssh-agent for
the same functionality.
> Developers have val
> > To the owner of this list:
> >
> > I suggest that the list is closed to the subscribers only.
> Quite a lot
> > of spam is being sent there.
> > What do you think ?
>
> I suggest they use ordb.org to lock out the spam from
> open relays. Most
> of the messages I've seen here as spam
> > Here is the line in loginfo that worked in v1.10:
> >
> > DEFAULT /usr/ucb/Mail -s "CVS Update: %{sv}" ${USER}@nvs.com
>
> This change was inadvertently omitted from NEWS -- the substitution is
> now inside double quotes rather than single quotes (this allows us to
> support files w
I'm trying to find out if there's been a change to the way CVS
handles mail triggers in the info files. Specifically, I am
having mail woes using 1.11p1.
What used to work just dandy in v1.10 is now broken in v1.11p1.
It seems as though the single quotes have been removed from
the subject line.
Sorry, I've gotta jump in for a minute... Greg is right about
SSH v pserver, however.
> > There's only _EXACTLY_ one case where cvspserver is in any way more
> > secure than giving out real accounts, and that's when
> > pserver is used to
> > give read-only anonymous access to a _copy_ of a repo
I am trying to connect to my CVS server via SSH2 and public key,
and it is hanging my connection. I checked the archives, and some
have had similar problems, and have stated that it's an SSH bug.
Listed below is my scenario, s/w versions, etc. Can someone please
offer a suggestion as to what th
> On Thu, Feb 14, 2002 at 06:33:18PM -0500, Douglas Finkle wrote:
> > Thoughts, references, examples?
>
> Don't know if this will help, but here's a key I use for
> port-forwarding a pop3 connection to give you an idea of the general
> format:
>
> comma
> > I'm looking for an example of a SSH public key that
> > has the special "command=" format for CVS. I'm setting
> > up CVS server access, and want to be very explicit what can
> > be done w/ the key.
> >
> > Can anyone, Greg?, provide an example of what the key
> should look like?
>
> "man s
> I'm looking for an example of a SSH public key that
> has the special "command=" format for CVS. I'm setting
> up CVS server access, and want to be very explicit what can
> be done w/ the key.
>
> Can anyone, Greg?, provide an example of what the key should
> look like?
I should also state th
I'm looking for an example of a SSH public key that
has the special "command=" format for CVS. I'm setting
up CVS server access, and want to be very explicit what can
be done w/ the key.
Can anyone, Greg?, provide an example of what the key should look like?
TIA,
Doug
__
> > Douglas Finkle writes:
> >
> > Sorry, but can you provide a reference url, or ftp
> > path for this update?
> > I checked out on
> http://ccvs.cvshome.org/servlets/ProjectDownloadList
> > and the last version posted was v1.11p1 on 2001-10-16.
>
> It has been brought to my attention that CVS 1.11.1 and
> 1.11.1p1 have a
> bug in pserver mode that allows read-only users to run the "tag"
> command. This allows read-only users to add and, more
> importantly, move
> or delete tags. The bug does not affect releases prior to 1.11.1 and
> ha
> >Directory hierarchy (InstallShield project) checked into CVS
> >filled with a few files, but mostly empty directories. The
> >directory hierarchy is required by InstallShield, not me.
>
> Empty directories are not supported well in CVS. If your project
> requires some empty directory structur
Scenario:
Directory hierarchy (InstallShield project) checked into CVS
filled with a few files, but mostly empty directories. The
directory hierarchy is required by InstallShield, not me.
Problem:
On the trunk everything checks out complete w/ various empty dirs,
and all is fine. On a branch h
> Scott O. writes:
> >
> > Can you use pserver to authenticate for multiple
> repositories? If so what
> > would the xinetd.conf look like. Thanks.
>
> Yes, just have multiple --allow-root= options:
>
> server_args = -f --allow-root=/u/cvs1
> --allow-root=/u/cvs2 pserver
FWIW, in Sol
>> > Disclaimer: I think this is all...
Oh yeah, admin user cvs should be in all groups... cvs, public, company[abc]
> =
> Thanks for the detailed answer!
ur welcome.
> Now for the trick question: If I am not going to use pserver, what is
> the easiest to set up, a
> On Thu, Jan 24, 2002 at 05:44:51PM +0100, Olav Lindkjølen wrote:
> > In short:
> > ---(Admin) must have read/write access to all modules.
> > ---Users from Company B must have read/write access only to
> modules with
> > code owned by them.
> > ---Users from Company B must allso have Read Only
uting table for supporting multiple NOCs.
--
Thanks for the insight.
-Doug
--
Douglas Finkle
Genuity, Inc.
40 matches
Mail list logo
