RE: CVS File Move
You are correct, but technically speaking, no historical information is lost, because the commit comment is stored on the dead revision created when the removal is committed. Presumably, the user remembers to make a descriptive comment. However, the history of the file becomes disjointed and it becomes hard to figure out everything that has happened to the file trans-move. --- Forwarded mail from [EMAIL PROTECTED] Assumming that is true then no historical information is preserved. That is to say you cannot move a file and its history without tinkering directly with the repository. It does not matter if you wait to commit or commit the remove and then commit the add, the result is the same? -Original Message- From: Paul Sander [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 1:01 PM To: Rod Macpherson; [EMAIL PROTECTED] Subject: Re: CVS File Move CVS never assumes you want to "move" the file. In this case, it assumes you want to remove a file from one place and add a new file in a different place, because that's what you told it you want to do. The only association made between the two files is in the user's mind and maybe in comments stored in the source code or in the revision logs. This is true even if both actions are processed by the same commit. --- Forwarded mail from [EMAIL PROTECTED] To clarify the movement of files, when you remove a file X from module /foo then add file X to module /bar CVS will assume you meant to move the file provided you did not commit. In general I do not want CVS to assume a relationship between a file X that was removed and a file X that is later added in a new location. That assumption is only made when CVS has a pending remove of a file with the same name. Is that correct? --- End of forwarded message from [EMAIL PROTECTED] --- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS File Move
Assumming that is true then no historical information is preserved. That is to say you cannot move a file and its history without tinkering directly with the repository. It does not matter if you wait to commit or commit the remove and then commit the add, the result is the same? -Original Message- From: Paul Sander [mailto:[EMAIL PROTECTED] Sent: Monday, October 06, 2003 1:01 PM To: Rod Macpherson; [EMAIL PROTECTED] Subject: Re: CVS File Move CVS never assumes you want to "move" the file. In this case, it assumes you want to remove a file from one place and add a new file in a different place, because that's what you told it you want to do. The only association made between the two files is in the user's mind and maybe in comments stored in the source code or in the revision logs. This is true even if both actions are processed by the same commit. --- Forwarded mail from [EMAIL PROTECTED] To clarify the movement of files, when you remove a file X from module /foo then add file X to module /bar CVS will assume you meant to move the file provided you did not commit. In general I do not want CVS to assume a relationship between a file X that was removed and a file X that is later added in a new location. That assumption is only made when CVS has a pending remove of a file with the same name. Is that correct? --- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS File Move
CVS never assumes you want to "move" the file. In this case, it assumes you want to remove a file from one place and add a new file in a different place, because that's what you told it you want to do. The only association made between the two files is in the user's mind and maybe in comments stored in the source code or in the revision logs. This is true even if both actions are processed by the same commit. --- Forwarded mail from [EMAIL PROTECTED] To clarify the movement of files, when you remove a file X from module /foo then add file X to module /bar CVS will assume you meant to move the file provided you did not commit. In general I do not want CVS to assume a relationship between a file X that was removed and a file X that is later added in a new location. That assumption is only made when CVS has a pending remove of a file with the same name. Is that correct? --- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS File Move
Title: Message To clarify the movement of files, when you remove a file X from module /foo then add file X to module /bar CVS will assume you meant to move the file provided you did not commit. In general I do not want CVS to assume a relationship between a file X that was removed and a file X that is later added in a new location. That assumption is only made when CVS has a pending remove of a file with the same name. Is that correct? TIA, Rod ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Relocating Directories
Technically speaking, no history is lost. In practice, these actions are not sufficient. If you have branches, then you may want to somehow replicate some of them to the new location as well. CVS doesn't help with that at all. Also, if you want to merge between branches in your before- and after-rename source trees, you must go through a lot of steps to create source patches in the old location and install them in the new location. "cvs log" also produces fragemented histories, which are at best glued together with comments that users must remember to enter by hand. In this specific case, munging the modules database might be a higher quality solution for what you want. Note that this action has its own limitations, and thus is also not a general purpose solution to the rename problem. >--- Forwarded mail from [EMAIL PROTECTED] >I have a sub-tree foo and I want to move it from /old/foo to /new/foo >where "old" is a top-level module and "new" is a top-level module. >1. Create a copy of /old/foo in /new/foo using cvs export. >2. Physically remove the files in /old/foo while preserving the CVS >folders. >3. Remove the contents of /old/foo using cvs remove. >4. Add the new files in /new/foo using cvs add. >5. Commit the changes to /new then commit the changes to /old. >Will this preserve my history? >--- End of forwarded message from [EMAIL PROTECTED] ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Relocating Directories
Title: Message I have a sub-tree foo and I want to move it from /old/foo to /new/foo where "old" is a top-level module and "new" is a top-level module. 1. Create a copy of /old/foo in /new/foo using cvs export. 2. Physically remove the files in /old/foo while preserving the CVS folders. 3. Remove the contents of /old/foo using cvs remove. 4. Add the new files in /new/foo using cvs add. 5. Commit the changes to /new then commit the changes to /old. Will this preserve my history? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: pserver never starts running
> Hello all,
> I am having trouble with my cvs remote login. It appears that my
> pserver doesn't start running.
>
Under what circumstances?
> My OS is Redhat 9.0
>
> It is running xinetd
>
> My /etc/xinetd.d/cvspserver file looks like this
>
> # default: off
> # description: An internal xinetd service, listing active services.
> service services
> {
> disable= no
> id= cvspserver
> env= HOME=/home/cvs
> port= 2401
> socket_type= stream
> protocol= tcp
> wait= no
> user= root
> passenv=
> server= /usr/bin/cvs
> server-args= --allow-root=/var/lib/cvsroot pserver
> }
>
> When I type:
> telnet [host] 2401 from my windoze machine is says: "Connection to
> [host]...Could not open a connection to host on port 2401 : Connect
> failed. ([host] is either jake or 192.168.0.155)
>
Have you rebooted or anything since putting this in cvspserver?
Or typed
kill -SIGUSR2 xinetd
as root, to get xinetd to reread its configuration files?
If you've done either of these, then I don't know what could be
going on.
David H. Thornley| If you want my opinion, ask.
[EMAIL PROTECTED] | If you don't, flee.
http://www.thornley.net/~thornley/david/ | O-
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: pserver never starts running
Pelemele Malef'carum writes: > > service services I doubt that you have an entry for "services" in your /etc/services; that should almost certainly be "service cvspserver" instead. > env= HOME=/home/cvs Why are you forcing a setting for $HOME? Without that, CVS will set it appropriately for each user as they connect. > passenv= Not even $PATH? > server-args= --allow-root=/var/lib/cvsroot pserver There should be a "-f" in there, too. There's an example configuration for xinetd in the CVS manual, have you read it? -Larry Jones Shut up and go get me some antiseptic. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
