[ In any case, I would prefer a simpler solution, in which I dont need to check
stderr, and preferrably even not stdout, only the exit status of a command. This is
because the algorithm needs to run in several environments. ]
Whatever cvs command you run you have to parse the text output. You
Hi,
I have understood the sticky tag/date but I have some problem with the
sticky options and the keyword substitution.
Could someone help me to understand what are and how to use them ?
Thanks,
Mimmo
___
Info-cvs mailing list
[EMAIL PROTECTED]
If you do it from the command line it will be reset when you reboot your
machine however.
|-+-
| | Kristopher Hollingsworth [EMAIL PROTECTED]|
| | Sent by:
in admin preferences you should set the correct settings for the
repositoty.
probably you're using pserver so you must go in Settings (in the same
preferences dialog) and check the first option (For 'pserver' (password)
port: 2401)
now go in admin command line and in the CVS command line
Hello to everybody,
Recently I ran into really annoying problem double spacing . And I really need you
advice guys.
This is a description of the problem :
I have CVS Server and several developers are working with it from their windows boxes,
I imported package into cvs repository by
Uri Abramov writes:
MIME-Version: 1.0
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
I have CVS Server and several developers are working with it from
their windows boxes, I imported package into cvs repository by moving
source code from
I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having much luck and don't see any solution
laid out clearly in the mailing lists.
I have a commitinfo file...
DEFAULT dos2unix
When I commit my Windows text file...
~/webapps cvs ci -m
On Fri, 13 Jun 2003, Andy Kriger wrote:
I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having much luck and don't see any solution
laid out clearly in the mailing lists.
CVS in client-server mode already performs the conversions.
(You
At 11:47 AM 6/13/2003, Andy Kriger wrote:
I am trying to setup our Unix-based CVS repository to run dos2unix when
files are committed, but I'm not having much luck and don't see any solution
laid out clearly in the mailing lists.
Don't attempt to use a commitinfo script to change a file being
Thank you all for all the help you've already given me, and here is where I am at,
I've got the repository set up in c:\ACS\Standard\Vol002\ACS.402\CVSROOT, I've got
another directory called Work for the checked out files, the Repository is on this
machine. So when running WinCVS what do I
Domenico Barlafante [EMAIL PROTECTED] writes:
I have understood the sticky tag/date but I have some problem with the
sticky options and the keyword substitution.
Could someone help me to understand what are and how to use them ?
The Sticky Options given by the 'cvs status' command will only
Thanks for the suggestions. I'll try those ideas.
As background, what is prompting this need is multiple developers with
different IDEs making connections to CVS. Since there's no way to be sure
what line format is being used, I'm looking for consistency.
-Original Message-
From:
At 03:25 PM 6/13/2003, Andy Kriger wrote:
As background, what is prompting this need is multiple developers with
different IDEs making connections to CVS. Since there's no way to be sure
what line format is being used, I'm looking for consistency.
Good luck.
The way to decrease the chances of
Andy Kriger writes:
As background, what is prompting this need is multiple developers with
different IDEs making connections to CVS. Since there's no way to be sure
what line format is being used, I'm looking for consistency.
You've got hold of the wrong end of the stick. It is the
Ok sorry for the screwed up emails I have been sending around, I might
have this one addressed correctly :-)
Most of the info here has already been mentioned, a small part that
we experienced has been left out. The cygwin cvs client does not
fix up the line endings on the commit. At least the
mike walster writes:
The cygwin envinronments
are installed with unix style the default for that system.
That is the root of your problem. You should *NEVER* install cygwin
with Unix line endings -- if you want a Unix-like system, you know where
to find it. Having some of your tools use one
On Fri, Jun 13, 2003 at 06:01:18PM -0400, Larry Jones wrote:
What do you mean by [line-ending problems] causing merges to panick? I can see
causing the
developer to panic since the entire file will be completely different
from CVS's perspective, but CVS shouldn't have a problem with it.
I
One must be carefull about the words one chooses here
I did indeed use the term panick spelled with a ck loosley.
The files do show up completely different which was causing
the developer to panick somewhat.
As I recall the instructions for cygwin say to always install
as unix line endings. I
18 matches
Mail list logo