Hi all
I work with cvs 1.11.1p1 on NT4.0 with a local repository. Usually it works
quite well. But sometimes it has a problem with filename cases like the
following:
cvs.exe -q -n update N:\Temp\Pec3kcvs4
U N:\Temp\Pec3kcvs4/OS/Src/CINOSFixed32.cpp
U N:\Temp\Pec3kcvs4/Os/Src/CINOSFixed32.cpp
This is not related
to CVS directly but I am sure there are people who would know the
answer...
WinCVS, after its
1.2 release has gone through 8 beta releases in the 1.3 product line.
Does anyone know
when WinCvs expects to make a stable release of 1.3 ?
-arcin
Arcin Bozkurt wrote:
This is not related to CVS directly but I am sure there are people who
would
know the answer...
WinCVS, after its 1.2 release has gone through 8 beta releases in the
1.3
product line.
Does anyone know when WinCvs expects to make a stable release of 1.3 ?
You
Does anyone know where the list of recognisable embedded commands for this
mailing list can be found?
The web page refers to a FAQ, but doesn't give a link to one.
Other mailing lists I subscribe to provide such things as '--LongSig' to
truncate long, corporately applied signatures from the
I have to sync two CVS repositories located on two non-
connected networks. (yep, this means tape/CDROM transports,
I know it sounds silly). I was wondering if there is a
better way than creating incremental tar files on both sides
and applying them on the other side. Luckily, the chances
On Fri, Aug 09, 2002 at 09:09:37AM +0200, Anders Truelsen wrote:
From: Mads Pultz [mailto:[EMAIL PROTECTED]]
Sent: 9. august 2002 07:27
To: [EMAIL PROTECTED]
Subject: Share repository between Linux and XP server
I have a dual-boot boot machine. Regardless of the OS I booted I want to
*** Before acting on this e-mail or opening any attachment you are advised to read the
disclaimer at the end of this e-mail ***
Hi
Bear in mind that Linux is case-sensitive but Windows is only
case-preserving. If you're not careful, some weirdness may
result from that.
And (you probably
Paul Grenyer wrote:
*** Before acting on this e-mail or opening any attachment you are advised to read
the disclaimer at the end of this e-mail ***
Hi
Bear in mind that Linux is case-sensitive but Windows is only
case-preserving. If you're not careful, some weirdness may
result from
Zieg, Mark wrote:
I have to sync two CVS repositories located on two non-
connected networks. (yep, this means tape/CDROM transports,
I know it sounds silly). I was wondering if there is a
better way than creating incremental tar files on both sides
and applying them on the other side.
Mark Cooper wrote:
Does anyone know where the list of recognisable embedded commands for this
mailing list can be found?
Well, the web admin page, as listed below, at
http://mail.gnu.org/mailman/listinfo/info-cvs, contains the options.
There aren't many, though.
The web page
Mike Ayers wrote:
Mark Cooper wrote:
The web page refers to a FAQ, but doesn't give a link to one.
Hmm?? A CVS FAQ? I'm not aware of one.
There's one up on http://cvshome.org. Follow the link in the left
navbar to the CVS FAQ. It isn't extraordinarily well maintained, but
All,
We are trying to stand up CVS on a Windows 2000 machine. We can get things
checked in locally, but when we try to push them to the server, we get a
permissions failure of unrecognized user/password.
Thanks,
Lynne
___
Info-cvs mailing list
I have to sync two CVS repositories located on two non-
connected networks.
If you MUST do this (and it is almost certain that you do
not need to, but that's another story)
I assume that you've never had to develop under DOD-enforced contract
requirements, or you wouldn't have written
There has been a fair amount of discussion about this topic in the past,
and I believe that someone has a working implementation that follows this
model:
Each site owns its own trunk. Each site creates a branch that is used for
importing from the other site(s); these branches map to the
Zieg, Mark wrote:
I have to sync two CVS repositories located on two non-
connected networks.
If you MUST do this (and it is almost certain that you do
not need to, but that's another story)
I assume that you've never had to develop under DOD-enforced contract
requirements, or you
On Fri, Aug 09, 2002 at 12:50:06PM -0700, Paul Sander wrote:
Each site owns its own trunk. Each site creates a branch that is used for
importing from the other site(s); these branches map to the trunk(s) at the
remote site(s). No local commits are permitted on the import branches.
Each site
--- Forwarded mail from [EMAIL PROTECTED]
On Fri, Aug 09, 2002 at 12:50:06PM -0700, Paul Sander wrote:
Each site owns its own trunk. Each site creates a branch that is used for
importing from the other site(s); these branches map to the trunk(s) at the
remote site(s). No local commits are
17 matches
Mail list logo
