attic
I just had my first encounter with a file being in the Attic. I have read the page in the manual about what this means, and I am confused. It says the head revision on the trunk has state dead. A dead state means 1) has been removed 2) never added, for that revision I have case 2). and it says If you add a file on a branch, it will have a trunk revision in 'dead' state, and a branch revision in a non-dead state. Could some one give a clearer meaning to me on this, sorry my brain doesn't seem to comprehend this today. Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
viewing conflicts without really doing update -j
When you do a cvs update -j branch_name, you see all the files in the module fly by and it tells you whether there is a conflict or whatever. Is there a way to do this (see what would happen), without it really doing it? Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
going back to the trunk on update
Hi, I did cvs update -r bra-1_0 file Now my file is on the branch. However I want to change it back to being the trunk, just the latest trunk version. I know I can look in the repository for the head version number but is there an easier way? Thanks in advance Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
viewing branch info for non current working copy
I was wondering is there a way to see what other versions there are for a file in the repository. My problem is the following. I have a certain revision checked out, however I would like to do a diff on another version (which I do not know the number or name). So without looking in the actual repository and finding the names/version numbers is there any other way to do this? Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
difference between 1.1 and 1.1.1.1
I was wondering what is the difference between 1.1 and 1.1.1.1? I have an import that the files are the same but other info is different? RCS info that is. Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
branch info
I just reread the rcsfile man page and had the following question. This
question might be answered if I read the source code to cvs, but I
haven't yet.
Basically, why do you need have
branches{num}*;
under the delta node (grammar).
It seems to be redundant because the
num
that is listed for the given delta has all that information (branch
points).
ex. If the node num is 1.2.2.1
Why have 1.2.2.1 in the branch field, unless I read the man page wrong
it says that it is showing the points for which it is a branch point,
which is shown in the num field.
?? am I confused?
Ron
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
Re: branch info
But you can tell this information by just looking at num ex. 1.2.2.1 (means it branched at 1.2), however if you look at 1.2 it says branch 1.2.2.1 is a branch rooted at itself, which is the exact same information. It looks to me how you chose to write your programs to get the data. For people writing parsers (myself), if you don't know any information on the given ,v file, it is simple to just take all the num information from delta and construct the graph. The alternative is to follow the branches that are listed under the given branch point. I can't say which is better, but both give me the same information. Actually num is faster for parsing since you just divide it out to get branch points. Opinion Kaz? Ron You wouldn't have 1.2.2.1 in the branch field for that node. What you would have is zero or more numbers referring to nodes that start branches based on that node. Their numbers would be 1.2.2.1.X.1 where X is some even integer. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: branch info
I agree, well unless someone tells me that the information is incorrect then num is good enough for parsing in my book. Thanks Kaz, Ron On Wed, 2003-06-18 at 16:19, Kaz Kylheku wrote: On 18 Jun 2003, Ronald Petty wrote: But you can tell this information by just looking at num ex. 1.2.2.1 (means it branched at 1.2), however if you look at 1.2 it says branch 1.2.2.1 is a branch rooted at itself, which is the exact same information. I think that the RCS file format is more flexible than the constraints that CVS imposes on it for its own purposes. RCS branching is more flexible with the numbering, from what I can recall. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
rev/branch?
I am still working on my rcs/cvs parser. I have a question on changing
the revision number / branch number etc.
If someone changes a number, will cvs still be able to recreate the
revision? If so does that mean a branch number if changed is still
going to be 2.revision_number?
Or instead of wondering what the numbers are, should I always parse
next {num} and follow it?
Just making sure it is correct?
Thanks
Ron
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
binary file ?
I have uploaded some images and pdfs and various other binary data. Everything like (png,jpg etc) all view fine when I use cvs and then view the files. I have not tried to change an image and then commit it yet. Is this why it still is viewing correctly? Because I haven't screwed it up with a new revision? I know you could add -kb file and it do something as binary. But since I didn't do that at first am I sol? Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Files beginning with a minus sign
What about cvs commit -filename.txt ? or cvs commit ./-filename.txt Ron On Fri, 2003-03-28 at 12:14, Eric Siegerman wrote: On Fri, Mar 28, 2003 at 11:15:43AM +, Franky Van Liedekerke wrote: cvs commit -m message -- -filename.txt So now the cvs command itself ws happy, but the server complains with: up-to-date check failed for -filename.txt Here are some possibilities (*not* tested): 1. cvs commit ./-filename.txt Forward slash to hopefully keep CVS happy 2. cvs commit .\-filename.txt Backslash to hopefully keep Windows happy 3. Same as (1), but do it on a UNIX box 4. Same as (1), but do it on the CVS server itself, in a local (i.e. non-client-server) sandbox If all else fails, and if you don't need the file's revision history (but think twice about this!): 5. Just go into the repo and rm ./-filename.txt,v (I know the ./ will keep rm happy; that variant I *have*, umm, tested, on a number of occasions :-) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / A distributed system is one on which I cannot get any work done, because a machine I have never heard of has crashed. - Leslie Lamport ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
ext ssh on windows
Is there a way to run cvs on windows through a script WITHOUT cygwin? Basically I want a dos window to be open and the user can ext with ssh to do the normal basic commands like co, update, add etc. Also is there a command line version of ssh that could work like this? Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: :ext: , ssh :pserver: relation question
So could someone explain what is going on then with ext and RSH_CVS? For example, when I do export RSH_CVS=ssh export CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot then cvs co somemodule what is actually happening is ssh [EMAIL PROTECTED] 'cvs -d /cvsroot co somemodule' Is this correct? Ron On Tue, 2003-03-25 at 03:18, Wolfgang Mettbach wrote: Hello, Mark D. Baushke wrote: Ronald Petty [EMAIL PROTECTED] writes: Could someone explain the difference between using :ext: (with CVS_RSH=ssh) over using pserver and having tcpwrapper listen on 2401? ... ... With pserver, your password is kept in a trivially obscured token in a $HOME/.cvspass file and sent over the network in the clear. Once you The file .cvspass seems to be created on Linux systems only. When I use WinCVS running on MS Bluescreen to connect to a pserver I can't find any file like .cvspass anywhere on my harddisks. Does WinCVS store the password at all or does it just keep it in memory? What about other IDEs like Eclipse? Has anyone experience with this concerning password management? ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: :ext: , ssh :pserver: relation question
Ops, I meant CVS_RSH. So I was close :). Thanks for pointing out -t.
I do have ssh-agent set up and running. Just was curious of what was
REALLY happening behind the scenes. Thanks for the help.
Ron
On Tue, 2003-03-25 at 14:29, Mark D. Baushke wrote:
Ronald Petty [EMAIL PROTECTED] writes:
So could someone explain what is going on then with ext and RSH_CVS?
Nothing at all happens in this case as RSH_CVS is not the environment
variable that is consulted by the :ext: method.
For example,
when I do
export RSH_CVS=ssh
Try using this:
export CVS_RSH=ssh
if you want to use ssh as your transport. You may also find it useful to
use 'ssh-agent' as a place to hold your credentials so that you are not
prompted for a passphrase for every cvs command.
export CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot
then
cvs co somemodule
what is actually happening is
ssh [EMAIL PROTECTED] 'cvs -d /cvsroot co somemodule'
Is this correct?
Almost correct.
You can see what is actually happning if you use the 'cvs -t co
somemodule' command. Basically, what happens is the equivalent of this
command:
${CVS_RSH:-rsh} -l user someserver ${CVS_SERVER:-cvs} server
and then the client communicates with the remote server to cause the
checkout to happen on the server and the differences to be transfered
back to the client.
Good luck,
-- Mark
On Tue, 2003-03-25 at 03:18, Wolfgang Mettbach wrote:
Hello,
Mark D. Baushke wrote:
Ronald Petty [EMAIL PROTECTED] writes:
Could someone explain the difference between using :ext: (with
CVS_RSH=ssh) over using pserver and having tcpwrapper listen on 2401?
...
...
With pserver, your password is kept in a trivially obscured token in a
$HOME/.cvspass file and sent over the network in the clear. Once you
The file .cvspass seems to be created on Linux systems only. When I use
WinCVS running on MS Bluescreen to connect to a pserver I can't find any
file like .cvspass anywhere on my harddisks.
Does WinCVS store the password at all or does it just keep it in memory? What
about other IDEs like Eclipse? Has anyone experience with this concerning
password management?
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
:ext: , ssh :pserver: relation question
Could someone explain the difference between using :ext: (with CVS_RSH=ssh) over using pserver and having tcpwrapper listen on 2401? Why would one do either over the other? Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
unsubscribe doesn't seem to work
I am trying to use the web site to get off the list and it never lets me. Will the admin please step up and give a hand. Please Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: What forum to propose new port?
How did you get cvs working on the 400? I would like to know how you did that. Because we are trying to use CVS everywhere in my company, and the only ones not using it are ISeries guys (400). Ron -Original Message- From: Larry Jones [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 9:00 AM To: Terrence Enger Cc: [EMAIL PROTECTED] Subject: Re: What forum to propose new port? Terrence Enger writes: (*) What does it mean? Using an existing distribution of cvs executing on Win95, I have had some success (very small test, no observed problems) controlling ASCII source in the hierarchichal part of the IFS of OS/400. But I can see value in using cvs to control a wider variety of stuff on the 400, ordered by what I would deem to be descending value: source physical file members (there are *lots* of those in the world), EBCDIC files, database files. Others with better imaginations than I can extend the list. That looks like English, but I can't understand a word you said. I think you're going to have to educate us about the OS/400 environment before we can have an intelligent discussion. I feel obliged to note, however, that CVS was designed to version programming *source* files, not arbitrary files. As is frequently discussed here, unless the files are divided into lines that can be meaningfully processed with something like the Unix 'diff' command, CVS really isn't a very effective tool. (*) How much of this change can the main line of development tolerate? I note for example, your discussion multiplatform sofware desing problem on bug-cvs with Dimitry Naldaev [EMAIL PROTECTED], where you take a position against having cvs do code conversions. I can imagine that much--but not all--of the necessary code would be segreated into a platform-specific subdirectory. CVS was really designed to work in an ASCII environment. The only solution I can imagine for Dimitry's problem would be to rewrite CVS to use some universal character set (say, ISO 10646) internally (i.e., in the code, in the repository, in the client/server protocol, etc.) and convert between that and the system character set on I/O. That would be an enourmous amount of work, I suspect it would be difficult to do it in an upward compatible form, it would probably make the repository files incompatible with RCS, it would significantly increase the size of most people's repositories, it would undoubtedly slow down CVS operations, and it would probably be a portability problem. Changing CVS to work in an EBCDIC-only enviroment should be much less work and have much less impact. Even if you do have to interoperate between EBCDIC and ASCII, that shouldn't be too much more difficult since it is easy to define a useful, invertable mapping between ASCII and EBCDIC. (Unfortunately, it is so easy that there are lots of them, which could present a problem if all your users can't agree on a single one.) In my limited study of the code, I see platform-specific files mapping one function to different facilities of the platform but no example of one platform providing more functionality than another. Is there any case where you would like to exploit the particular demands or capabilities of a particular platform? Two special cases could make a pattern; one special case would likely just make a mess. I can't think of any. The general philosophy is that CVS should work the same way everywhere. -Larry Jones Aw Mom, you act like I'm not even wearing a bungee cord! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: Software Position
Who is the admin for this list, can you remove me? There is too much junk on this list. Thanks Ron ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
