At 17:12 -0400 4/21/00, Joseph Noonan wrote:
>When we run a cvs update, some of the files had a P in from of them. I can
>find no reference to P. What does this stand for?
>
>Joseph G. Noonan
>Product Development
"Patch". The file was updated with a small difference patch, instead
of copying
Rui Cordeiro wrote:
> Is there any option to tell to the cvs update to ignore the files that are in the
>repository but not in the working directory.
> I want to update, in one step, only the files that I have checkout.
Don't pass '-d' to update?
Derek
--
Derek Price CVS
On Wed, Mar 21, 2001 at 02:54:18PM -0500, Derek R. Price wrote:
> Rui Cordeiro wrote:
>
> > Is there any option to tell to the cvs update to ignore the files that are in the
>repository but not in the working directory.
> > I want to update, in one step, only the files that I have checkout.
>
>
Eric Siegerman wrote:
> On Wed, Mar 21, 2001 at 02:54:18PM -0500, Derek R. Price wrote:
> > Rui Cordeiro wrote:
> >
> > > Is there any option to tell to the cvs update to ignore the files that are in
>the repository but not in the working directory.
> > > I want to update, in one step, only the
"Derek R. Price" wrote:
>
> Eric Siegerman wrote:
>
> > On Wed, Mar 21, 2001 at 02:54:18PM -0500, Derek R. Price wrote:
> > > Rui Cordeiro wrote:
> > >
> > > > Is there any option to tell to the cvs update to ignore the files that are in
>the repository but not in the working directory.
> > >
"David H. Thornley" wrote:
> "Derek R. Price" wrote:
> >
> > Eric Siegerman wrote:
> >
> > > On Wed, Mar 21, 2001 at 02:54:18PM -0500, Derek R. Price wrote:
> > > > Rui Cordeiro wrote:
> > > >
> > > > > Is there any option to tell to the cvs update to ignore the files that are
>in the repository
On Wed, Mar 21, 2001 at 03:34:17PM -0600, David H. Thornley wrote:
> "Derek R. Price" wrote:
> > Eric Siegerman wrote:
> > > On Wed, Mar 21, 2001 at 02:54:18PM -0500, Derek R. Price wrote:
> > > > Rui Cordeiro wrote:
> > > >
> > > > > Is there any option to tell to the cvs update to ignore the fil
Eric Siegerman writes:
>
> That'll prevent fetching of un-checked-out directories, but I
> know of no way to prevent the fetching of un-checked-out files
> within a directory that *is* checked out.
Create CVS/Entries.Static like CVS does when you only checkout some of
the files in a directory.
Pavan Seth writes:
>
> If i update say 1000 files...by issuing
> cvs update -d -P... result output scrolls fast..it is
> difficult for me to find which files has got
> conflicts?
Just do the command again -- there probably won't be any new updates so
you'll just get the locally modified files an
Pavan Seth wrote:
>
> If i do an cvs update -d -P
>
> I just need to print or log only those lines/files
> which got confilcts...is there any way?
>
> If i update say 1000 files...by issuing
> cvs update -d -P... result output scrolls fast..it is
> difficult for me to find which files
[EMAIL PROTECTED] wrote:
>
> Hello,
> is there a possibility to check out/update all files that were
> up-to-date at a certain point in time?
cvs [co|up] -D "date"
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-c
hi,
It will be the last committed timestamp according to me...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Jayashree
Sent: Friday, September 06, 2002 12:13 PM
To: [EMAIL PROTECTED]
Subject: cvs update
Hi,
$cvs status a.c
File: a.cStatus:
Jayashree writes:
>
> $cvs status a.c
> File: a.cStatus: Locally Modified
>Working revision:1.40Mon Sep 2 20:46:00 2002
>Repository revision: 1.40/home/cvs/a.c,v
>
> What does the time stamp " Mon Sep 2 20:46:00 2002" mean?
> Is that the checkout/update time or che
[EMAIL PROTECTED] writes:
>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
Please don't send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
> Cvs[update aborted]: cannot rename file .new.delludf.jar to delludf.jar:
> No such file or directory.
>
> Is thi
e
Gunjan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 07, 2002 4:23 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: cvs update
[EMAIL PROTECTED] writes:
>
> MIME-Version: 1.0
> Content-Type: multipart/alternative;
Pleas
[EMAIL PROTECTED] writes:
>
> The platform is windowsNT. It's a client server mode and I'm using
> cvsnt_1.11.1.3.
Is cvsnt the client as well as the server? (I don't know much about
cvsnt -- it's a separate line of development from the standard CVS.) If
so, perhaps you've found a bug, but I s
richard blair <[EMAIL PROTECTED]> writes:
> I perform a cvs update on a large directory structure, and a conflict
> happens, but the file it happened on is too far up to scroll to. Does
> anyone know how to retrieve that information? In other words, how do I
> find out which files were in conflic
Rich,
cvs update >update.txt ?
cvs update | less ?
Steve
On Thu, 2003-02-20 at 18:57, richard blair wrote:
> I perform a cvs update on a large directory structure, and a conflict
> happens, but the file it happened on is too far up to scroll to. Does
> anyone know how to retrieve that informa
Try using the attached perl script. It cleans up the display quite
nicely, with a summary at the end for things like conflicts, files in the
way, etc.
> I perform a cvs update on a large directory structure, and a conflict
> happens, but the file it happened on is too far up to scroll to. Does
>
You don't say what operating system you are using, but whatever it is you
should be able to redirect the output to a file, for example by doing:
cvs update > info.txt
Then you can browse the file with whatever text editor or viewer you like.
If you are using a Unix-alike you could use 'more inf
On Fri, Nov 14, 2003 at 12:27:01PM -0800, Richard Pfeiffer wrote:
> However, we have one project in this repository that now takes
> 1:58 to checkout and 1:29 to update. It used to update much
> faster; these 'slow' update times just started occuring.
Two stabs in the dark:
- Are you on a branc
Thanks Eric. I had actually thought of both of those and took quick looks:
1) There are no branches as of yet, so that nixed that thought!
2) I think the second thought is the one I need to investigate further. Just wanted to see if the list concurred, or had ideas I overlooked. I initially
On Fri, Nov 14, 2003 at 01:55:55PM -0800, Richard Pfeiffer wrote:
> The project in question (Proj A) and one
> I'm using for comparison look like this:
>
> Proj A is half the size as Proj B, but did have more directories. I might have to
> find out just how many more.
> Proj A took 2m15s to ch
Eric Siegerman writes:
>
> Didn't someone say that "co" locks the whole tree, but "update"
> only locks one directory at a time?
If they did, they're wrong. Checkout and update both use the same
underlying code, so they both do locking the same way (directory at a
time). I think admin, commit a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> i would like to setup a trigger for when cvs-update touches a file
> (updates or merges) in checked out work areas. is there already a
> mechanism for this?
No.
The Set-update-prog feature was removed for cvs 1.11.6. It i
Paul,
Use the "precommand" (or "postcommand") trigger.
http://www.cvsnt.org/manual/postcommand.html
This is only available in CVSNT 2.0.58 and later.
CVSNT is free (GPL - just like CVS) is available on Linux, Unix, Windows,
Mac OS X etc etc. If you are using WinCVS or TortoiseCVS then you are
a
Hi Vicki,
This is explained in page 110 of the Cederquist manual which essentially
says that,
P file : Like 'U' but the CVS server sends a patch instead of an entire file.
These two things (U and P) accomplish the same thing.
Rgs
Sriram
--- "Nelson, Vicki" <[EMAIL PROTECTED]> wrote:
>
That file has been updated by Patch (and not a full file-copy)
See Appendix A.16.2 in the Cederqvist manual.
-Original Message-
From: Nelson, Vicki [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 8, 2001 4:51 PM
To: '[EMAIL PROTECTED]'
Subject: cvs update question
I searched the CVS book
In article <[EMAIL PROTECTED]>, Ian Dall wrote:
>CVS does not seem to work properly for me. Since the problem
>is pretty basic, I assume it is my naivety, which is the problem
>rather than a bug. I'd appreciate if someone can enlighten me.
Your problem looks suspiciously like you blew the reposit
Colm Murphy writes:
>
> Is there any way to tell update to only update the files in my sandbox
> and not to pull in any other files ?
I'm not sure I understand what you want to do (or why), but I think
cvs update -lA *
may do what you want.
-Larry Jones
Some people just don't have i
Colm Murphy writes:
>
> What I would propose is the following update behaviour:
>
> (1) Update only the existing files in existing directories.
You can achieve that by doing "cvs update *".
-Larry Jones
In a minute, you and I are going to settle this out of doors. -- Calvin
_
[ On Thursday, February 21, 2002 at 11:06:28 (+), Colm Murphy wrote: ]
> Subject: CVS Update Behaviour
>
> All is fine until the developer does an cvs update.
> The current behaviour is that all existing files are updated (which is
> fine) but all other files in the directory are checked out.
[ On Thursday, February 21, 2002 at 10:23:16 (-0500), Larry Jones wrote: ]
> Subject: Re: CVS Update Behaviour
>
> Colm Murphy writes:
> >
> > What I would propose is the following update behaviour:
> >
> > (1) Update only the existing files in existing director
[ On Thursday, February 21, 2002 at 11:06:28 (+), Colm Murphy
wrote:]
> Subject: CVS Update Behaviour
>
> All is fine until the developer does an cvs update.
> The current behaviour is that all existing files are updated (which is
> fine) but all other files in the directory are checked out
[ On , February 21, 2002 at 18:06:53 (-0500), Arcin Bozkurt - Archie wrote: ]
> Subject: Re: CVS Update Behaviour
>
> suppose I created a branch at this point (for bugfixes) and later
> restructured the repository moving files around. I believe there is not
> way to merge the bu
On Thu, 2002-02-21 at 17:45, Greg A. Woods wrote:
> [ On , February 21, 2002 at 18:06:53 (-0500), Arcin Bozkurt - Archie wrote: ]
> > Subject: Re: CVS Update Behaviour
> >
> > suppose I created a branch at this point (for bugfixes) and later
> > restructured the reposi
[ On , February 21, 2002 at 18:55:21 (-0500), Arcin Bozkurt - Archie wrote: ]
> Subject: Re: CVS Update Behaviour
>
> On Thu, 2002-02-21 at 17:45, Greg A. Woods wrote:
> >
> > Don't get stuck on this idea of trying to keep track of everything back
> > to the beg
This is a flaw in CVS that tracks back to the modules file. While you
can set up modules like the one you are talking about, CVS only looks at
the modules file when you check out a module. Update, etc, don't check
against the modules file after that. This is why you are seeing this
behavior
On Thu, Feb 21, 2002 at 20:00:23 -0500, David Fuller sent 1.5K bytes:
> Colm Murphy wrote:
> >directory. This is setup by defining a module to contain only certain
> >files.
> >
> >All is fine until the developer does an cvs update.
> >The current behaviour is that all existing files are updated
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On , February 21, 2002 at 18:55:21 (-0500), Arcin Bozkurt - Archie wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> On Thu, 2002-02-21 at 17:45, Greg A. Woods wrote:
>> >
>> > Don't get stuck on
[ On Thursday, February 21, 2002 at 18:03:20 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> That last paragraph is utter crap. Without having the entire history
> of a file's lifetime in one container, it's much much harder to track
> changes that
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Thursday, February 21, 2002 at 18:03:20 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> That last paragraph is utter crap. Without having the entire history
>> of a file's lifetime in o
On Thu, 2002-02-21 at 21:03, Paul Sander wrote:
> >--- Forwarded mail from [EMAIL PROTECTED]
>
> >[ On , February 21, 2002 at 18:55:21 (-0500), Arcin Bozkurt - Archie wrote: ]
> >> Subject: Re: CVS Update Behaviour
> >>
> >> On Thu, 2002-02-21 at 17:45,
(I should know better than to get into this...)
On Fri, Feb 22, 2002 at 01:16:35AM -0500, Greg A. Woods wrote:
> It's hardly even noticably
> more difficult to track the history across multiple files.
Greg, *that* statement is complete and utter crap. Or, please post the
single *cvs* command t
[ On Friday, February 22, 2002 at 12:18:37 (-0600), Steve Greenland wrote: ]
> Subject: Re: CVS Update Behaviour
>
> (I should know better than to get into this...)
Yes, you really should!
> On Fri, Feb 22, 2002 at 01:16:35AM -0500, Greg A. Woods wrote:
> > It's hardly
[ On Friday, February 22, 2002 at 01:48:50 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> I've done it the "CVS way", actually I've done it in several of the
> "CVS ways" as documented in the manual.
Only one of the ways document
>--- Forwarded mail from [EMAIL PROTECTED]
>On Thu, 2002-02-21 at 21:03, Paul Sander wrote:
>> >--- Forwarded mail from [EMAIL PROTECTED]
>>
>> >[ On , February 21, 2002 at 18:55:21 (-0500), Arcin Bozkurt - Archie wrote: ]
>> >> Subject: Re: CVS Up
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Friday, February 22, 2002 at 12:18:37 (-0600), Steve Greenland wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> On Fri, Feb 22, 2002 at 01:16:35AM -0500, Greg A. Woods wrote:
>> > It's hardly even noti
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> I don't need to use any such over-burdened fancy
> system. I'm extremely
> happy with the way things work now in CVS -- there's
> more than adequate
> support for tracking renames across history, at
> least form the point of
> view of anyone actual
On Fri, Feb 22, 2002 at 02:14:21PM -0500, Greg A. Woods wrote:
> [ On Friday, February 22, 2002 at 12:18:37 (-0600), Steve Greenland wrote: ]
> > On Fri, Feb 22, 2002 at 01:16:35AM -0500, Greg A. Woods wrote:
> > > It's hardly even noticably
> > > more difficult to track the history across multipl
[ On Friday, February 22, 2002 at 12:05:34 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> I don't know about anyone else, but I use "cvs log" every time I do a
> "cvs update" to read other people's thoughts about the changes they&#
[ On , February 22, 2002 at 11:09:21 (-0500), Arcin Bozkurt - Archie wrote: ]
> Subject: Re: CVS Update Behaviour
>
> A question on merge behaviour of cvs: Will CVS be able to follow a file
> disappearing in one module, appearing in another one? I would say no.
> And therefore a
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Friday, February 22, 2002 at 12:05:34 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> I don't know about anyone else, but I use "cvs log" every time I do a
>> "cvs update&
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> [ On , February 22, 2002 at 11:09:21 (-0500), Arcin
> Bozkurt - Archie wrote: ]
> Of course a merge won't work across renames. Who
> cares? How often has
> this happened to you? The wording of your question
> suggests: NEVER.
Well, if I were us
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> [ On Friday, February 22, 2002 at 12:05:34 (-0800),
> Paul Sander wrote: ]
> How often have you had to run two or more commands
> to look at the
> history of a file across a rename? (which is what I
> asked in the first
> place)
Also, I'm curious
[ On Friday, February 22, 2002 at 14:45:32 (-0600), Steve Greenland wrote: ]
> Subject: Re: CVS Update Behaviour
>
> On Fri, Feb 22, 2002 at 02:14:21PM -0500, Greg A. Woods wrote:
> > [ On Friday, February 22, 2002 at 12:18:37 (-0600), Steve Greenland wrote: ]
> > > On Fr
[ On Friday, February 22, 2002 at 13:39:35 (-0800), Noel Yap wrote: ]
> Subject: Re: CVS Update Behaviour
>
> This is another one of those "CVS is perfect for what
> it does. It's not broken. And don't pay any
> attention to those other tools behind the curtain
[ On Friday, February 22, 2002 at 13:25:37 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> And every time a merge is done from a branch where a rename was done on
> one of the branches.
And what has been said about that for years now? DON'T DO THAT
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Friday, February 22, 2002 at 14:45:32 (-0600), Steve Greenland wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> On Fri, Feb 22, 2002 at 02:14:21PM -0500, Greg A. Woods wrote:
>> > [ On Friday, February 22
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Friday, February 22, 2002 at 13:25:37 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> And every time a merge is done from a branch where a rename was done on
>> one of the branches.
>And
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> Perhaps what I can now do intuitively is hard for
> someone else, but if I
> learned to do it intuitively then pretty much anyone
> can learn it too.
> I'm no superman and I don't believe I have a
> photographic memory or
> anything fancy like that
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> [ On Friday, February 22, 2002 at 13:25:37 (-0800),
> Paul Sander wrote: ]
> > Subject: Re: CVS Update Behaviour
> >
> > And every time a merge is done from a branch where
> a rename was done on
> >
Paul Sander writes:
>
> There's just one little problem with this: "cvs log" only works when
> a file is in your sandbox. If it's been removed and committed, then
> you must do something like "cvs rlog `cat CVS/Repository`/oldfile.c | less".
No, "cvs log" works just fine on a removed file:
jo
>--- Forwarded mail from [EMAIL PROTECTED]
>Paul Sander writes:
>>
>> There's just one little problem with this: "cvs log" only works when
>> a file is in your sandbox. If it's been removed and committed, then
>> you must do something like "cvs rlog `cat CVS/Repository`/oldfile.c | less".
>No
You're spreading F.U.D. and untruths again Paul.
[ On Friday, February 22, 2002 at 20:51:55 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> There's just one little problem with this: "cvs log" only works when
> a file is in your sandbox. If
[ On Friday, February 22, 2002 at 20:57:01 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> >--- Forwarded mail from [EMAIL PROTECTED]
>
> >[ On Friday, February 22, 2002 at 13:25:37 (-0800), Paul Sander wrote: ]
> >> Subject: Re: CVS Update
[ On Saturday, February 23, 2002 at 06:37:35 (-0800), Noel Yap wrote: ]
> Subject: Re: CVS Update Behaviour
>
> Because the tool is broken under such circumstances.
> It's broken because it claims to be concurrent, but
> under such circumstances, it's not.
Huh? What
; Subject: Re: CVS Update Behaviour
>
> --- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> > It seems perfectly simple and very quick when I do
> > it. Perhaps you
> > should try it:
> >
> > cvs log newfile.c | less
> >
> >
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> "patch" has been a "standard" tool in unix
> development for nearly two
> decades now. Prior to that the commonly used tool
> that can do the exact
> same job with only slightly less success and using
> the exact same tool
> to create the diff, was
een removed to the Attic in the
current release.
>[ On Friday, February 22, 2002 at 20:51:55 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>> In this latter case, you need to
>> know where in the repository the RCS file sits, and that info isn't
>
On 02-Feb-22 18:31, Greg A. Woods wrote:
> And what has been said about that for years now? DON'T DO THAT
It's time to give that a second thought, IMHO.
> > This involves several files every time a patch goes
> > out, if the project was reorganized since the code diverged. This
> > phonom
On 02-Feb-22 14:14, Greg A. Woods wrote:
> No, you're full of crap too if you think that's a necessary feature.
Frankly. Why does it hurt you that someone else needs something else from
your favourite tool?
I think renaming and moving files accross directories is nice to have.
I don't think it i
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Friday, February 22, 2002 at 20:57:01 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> >--- Forwarded mail from [EMAIL PROTECTED]
>>
>> >[ On Friday, February 22, 2
Hi Larry,
It turns out that CVS already does what I wanted all along!
If you don't checkout a complete directory CVS creates a Entries.Static
file in the CVS directory. When you do an update it will then only
update the existing files.
Colm A
Larry Jones wrote:
> Colm Murphy writes:
>
>>Wh
In article <[EMAIL PROTECTED]>, Nagy Gabor wrote:
>On 02-Feb-22 14:14, Greg A. Woods wrote:
>> No, you're full of crap too if you think that's a necessary feature.
>
>Frankly. Why does it hurt you that someone else needs something else from
>your favourite tool?
>
>I think renaming and moving file
In article <[EMAIL PROTECTED]>, Paul Sander wrote:
>>"patch" has been a "standard" tool in unix development for nearly two
>>decades now. Prior to that the commonly used tool that can do the exact
>>same job with only slightly less success and using the exact same tool
>>to create the diff, was c
--- Kaz Kylheku <[EMAIL PROTECTED]> wrote:
> In article
> <[EMAIL PROTECTED]>, Paul
> Sander wrote:
> >>"patch" has been a "standard" tool in unix
> development for nearly two
> >>decades now. Prior to that the commonly used tool
> that can do the exact
> >>same job with only slightly less succes
>--- Forwarded mail from [EMAIL PROTECTED]
>In article <[EMAIL PROTECTED]>, Paul Sander wrote:
>>>"patch" has been a "standard" tool in unix development for nearly two
>>>decades now. Prior to that the commonly used tool that can do the exact
>>>same job with only slightly less success and using
[ On Monday, February 25, 2002 at 00:17:58 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> Renames are not usually a requirement of maintenance, but they are a
> requirement of new development. Bug fixes are done during maintenance,
> and merged into new dev
[ On Sunday, February 24, 2002 at 20:13:51 (-0800), Noel Yap wrote: ]
> Subject: Re: CVS Update Behaviour
>
> --- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> > "patch" has been a "standard" tool in unix development for nearly two
> > decad
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
> [ On Monday, February 25, 2002 at 00:17:58 (-0800), Paul
> Sander wrote: ]
> > Subject: Re: CVS Update Behaviour
> >
> > Renames are not usually a requirement of maintenanc
[ On Monday, February 25, 2002 at 10:46:14 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> >--- Forwarded mail from [EMAIL PROTECTED]
> >
> >Free software development depends critically on patch. Just about anyone
> >involved in it must know ho
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Monday, February 25, 2002 at 00:17:58 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> Renames are not usually a requirement of maintenance, but they are a
>> requirement of new developme
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Sunday, February 24, 2002 at 20:13:51 (-0800), Noel Yap wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> --- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
>> > "patch" has been a "st
[ On Sunday, February 24, 2002 at 20:24:15 (+0100), Nagy Gabor wrote: ]
> Subject: Re: CVS Update Behaviour
>
> I think renaming and moving files accross directories is nice to have.
> I don't think it is necessary, in a way that I can live without this
> feature.
>
>
>--- Forwarded mail from [EMAIL PROTECTED]
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>>
>> [ On Monday, February 25, 2002 at 00:17:58 (-0800), Paul
>> Sander wrote: ]
>> > Subject: Re: CVS Update Behaviour
&
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Monday, February 25, 2002 at 10:46:14 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> >--- Forwarded mail from [EMAIL PROTECTED]
>> >
>> >Free software development d
[ On Sunday, February 24, 2002 at 22:09:31 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> Hmmm... Let's recap:
>
> >> cp $1 $2
> >> cvs rm -f $1
> >> cvs add $2
> >> cvs commit -m "moved $
On 02-Feb-25 17:54, Greg A. Woods wrote:
> > When I discovered cvs did not know this, I was puzzled, and sad.
> I am puzzled and sad that you could not figure this out on first meeting
> and learning CVS. It really should be as self evident as it is well
> documented in the manual.
That's where
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> [ On Sunday, February 24, 2002 at 22:09:31 (-0800),
> Paul Sander wrote: ]
> > Subject: Re: CVS Update Behaviour
> >
> > Hmmm... Let's recap:
> >
> > >> cp $1 $2
> >
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> Would you allow a dentist to work on your teeth if
> he or she didn't know
> of all the "standard" tools a dentist might need to
> do a good job fixing
> your teeth? Would you sit in the chair after you
> saw a lone pair of
> vice grips on the tray
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> You really need to learn more about how CVS works
> internally. If you
> had chosen CVS because RCS was insufficient for your
> needs then I think
> you would be happy not to have such a mapping layer.
> CVS handles
> renames by way of removing an
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Sunday, February 24, 2002 at 22:09:31 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> Hmmm... Let's recap:
>>
>> >> cp $1 $2
>> >> cvs rm -f $1
>>
[ On Tuesday, February 26, 2002 at 01:29:49 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> >BTW, 'patch' is a _standard_ Unix tool. It's documented in The Single
> >UNIX Specification, and it will be in IEEE Std. 1003.2b.
>
> Fine
[ On Tuesday, February 26, 2002 at 00:27:36 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> Why bother with "patch" when "merge" is better? Or even better yet,
> "cvs update"?
You haven't been paying attention, have you. The
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Tuesday, February 26, 2002 at 01:29:49 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> >BTW, 'patch' is a _standard_ Unix tool. It's documented in The Single
>> >UNIX
[ On Tuesday, February 26, 2002 at 10:27:23 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> inclusion, the relationship between the two files becomes variable.
> In the event that a file is moved into a shared module and at a later
> time the target file'
>--- Forwarded mail from [EMAIL PROTECTED]
>[ On Tuesday, February 26, 2002 at 10:27:23 (-0800), Paul Sander wrote: ]
>> Subject: Re: CVS Update Behaviour
>>
>> inclusion, the relationship between the two files becomes variable.
>> In the event that a file is moved
[ On Tuesday, February 26, 2002 at 16:19:11 (-0800), Paul Sander wrote: ]
> Subject: Re: CVS Update Behaviour
>
> >--- Forwarded mail from [EMAIL PROTECTED]
>
> >[ On Tuesday, February 26, 2002 at 10:27:23 (-0800), Paul Sander wrote: ]
> >> Subject: Re: CVS Update
--- "Greg A. Woods" <[EMAIL PROTECTED]> wrote:
> You really do know how to get off track and squirm
> out from under the
> pressure when you've been caught off-gaurd with a
> real answer to the
> original question you asked.
Actually, Paul's question, IIRC, was how many know and
use these tools o
1 - 100 of 181 matches
Mail list logo
