problem with the Tortoise ssh -pw password option
I know this is an insecure method, but I'm going crazy typing in my password every 2 seconds, and the pageant, puttygen, option keeps referring to Sourceforge example. The other examples I found didn't work for setting up public keys on the cvs server I'm using. but anyway So, it's bad when the 'lazy man's' alternative also craps out. My setup is: Tortoise 1.8.17 Tools > ssh params > -l "%u" "%h" -pw mycvspassword The reponse is an alert box: PuTTY Fatal Error Unable to authenticate Any ideas? Thanks, Ed "Too lazy to do all this? There is an alternative solution, which is insecure as it keeps your password in plaintext on your machine. Go to TortoiseCVS Preferences -> SSH -> SSH parameters and set the value to -pw password." http://www.tortoisecvs.org/faq.shtml#sshkeys ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How do I get a barebone stripped off list of files changedbetween 2 builds?
Ok that worked beautifully, thank you again. :)
Original Message Follows
From: Robert Clark <[EMAIL PROTECTED]>
To: info-cvs@gnu.org
Subject: Re: How do I get a barebone stripped off list of files
changedbetween 2 builds?
Date: Tue, 12 Jul 2005 16:40:05 -0400
MIME-Version: 1.0
Received: from lists.gnu.org ([199.232.76.165]) by mc9-f9.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211); Tue, 12 Jul 2005 18:38:23 -0700
Received: from localhost ([127.0.0.1] helo=lists.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43)id 1DsWDl-0003BE-94for [EMAIL PROTECTED]; Tue, 12 Jul
2005 21:39:33 -0400
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)id
1DsS0u-00053P-Tgfor info-cvs@gnu.org; Tue, 12 Jul 2005 17:10:01 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)id
1DsS0r-000520-QOfor info-cvs@gnu.org; Tue, 12 Jul 2005 17:09:59 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43) id 1DsS0q-000502-FOfor info-cvs@gnu.org; Tue, 12 Jul
2005 17:09:57 -0400
Received: from [12.106.87.68] (helo=irvbhxw02.prod.quest.corp)by
monty-python.gnu.org with esmtp (Exim 4.34) id 1DsRfn-0007kS-3Tfor
info-cvs@gnu.org; Tue, 12 Jul 2005 16:48:11 -0400
Received: from tormbxw01.prod.quest.corp ([10.4.100.91])
byirvbhxw02.prod.quest.corp with Microsoft SMTPSVC(6.0.3790.211); Tue, 12
Jul 2005 13:40:07 -0700
Received: from tor106065.prod.quest.corp ([10.4.114.58])
bytormbxw01.prod.quest.corp with Microsoft SMTPSVC(5.0.2195.6713);Tue, 12
Jul 2005 16:40:06 -0400
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Organization: Quest Software Inc.
User-Agent: KMail/1.8.1
References: <[EMAIL PROTECTED]>
X-Face:
@wf=R>`Gp1sqW"$*(jmq~x\Y:on!638~obu4W34T^iIADeQK]
K>WA}}rUgp4Ih&a3^:<~P&$|P|2"Ad=8J_&^Y.qHk1)8i[n/[#/~oi$,g(:/)gt6"Fm^GW!BBsD
+RP"I3Xb~I6OH#&2^==29GQ~5UAfE._cNv.V4{qdw2uBp
X-OriginalArrivalTime: 12 Jul 2005 20:40:06.0564
(UTC)FILETIME=[E3372640:01C58721]
X-BeenThere: info-cvs@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Announcements and discussions for the CVS version control
system
List-Unsubscribe:
,
List-Archive:
List-Post:
List-Help:
List-Subscribe:
,
Errors-To: [EMAIL PROTECTED]
Return-Path: [EMAIL PROTECTED]
On Tuesday July 12, 2005 03:58 pm, "S I" <[EMAIL PROTECTED]> wrote:
> I'm trying to get a stripped down list of files modified and
> committed between 2 builds or a build and my working folder in CVS.
> I would just like to see the path/filename only.
What I generally do is use the rdiff command with the -q and -s (for
shout output) options. Something like:
cvs -q rdiff -s -r TAG1 -r TAG2 module.
You can substitute any valid combination of -r and -D options to
restrict the output to the range you want. So in this case, your
example would be:
cvs -q rdiff -s -r HEAD -D yesterday your-module-name > cvsHist1.txt
- Rob
--
Robert J. Clark
[EMAIL PROTECTED]
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
MAKE MONEY
MAKE MONEY!!! MAKE THOUSANDS!!! WELL GUESS WHAT!!! Within seven days, I started getting money in the mail!! I was shocked!! I figured it would end soon, but the money just kept coming in. In my first week, I made about $25.00. By the end of the second week I had made a total of more than $1000.00!! In the third week I had more than $10,000.00 and it's still growing!! This is now my fourth week and I have made a total of $42,000.00 and it's still coming rapidly. It's certainly worth $6.00 and six stamps, and I have spent more than that on the lottery without ever winning!!! My fingers are sore from opening all the envelopes & I are on first name basis with our local post office. (i bet they are now doin it too!!) Let me tell you how this works and most important, why it works.. also make sure you print this out NOW, so you can get the information off of it, as you will need it. I promise you that if you follow the directions exactly that you will start making more money than you thought possible by doing something so easy!! Suggestion: Read this entire message carefully!! (Print it out or download it) Follow the simple directions and watch the money come in!! It's easy. It's legal. And, your investment is only $6.00 (Plus postage) !!! You can use any currancy as people can always change it.. IMPORTANT: This is not a rip-off, it is decent; it's legal; and it is virtually no risk - it really works!! If all the following instructions are adhered to, you will receive extraordinary dividends. PLEASE NOTE: Please follow the directions EXACTLY, and $50,000 or more can be yours in 20 to 60 days. This program remains successful because of the honesty and integrity of the participants. Please continue its success by carefully adhering to the instructions. You will now become apart of the Mail Order business. You are in the business of developing Mailing Lists. Many large corporations are happy to pay big bucks for quality lists. However, the money made from the mailing lists is secondary to income which is made from people like you and me asking to be included in that list. Here are the four easy steps to success. STEP ONE: Get six separate pieces of paper and write the following on each piece of paper "PLEASE PUT ME ON YOUR MAILING LIST." Now get 6 U.S. $1.00 bills and place ONE inside of EACH of the six pieces of paper so the bill will not be seen through the envelope (to prevent thievery). Next, place one paper in each of the six envelopes and seal them. You now should have six sealed envelopes, each with a piece of paper stating the above phrase, your name and address, and a $1.00 bill. What you are doing is creating a service. THIS IS ABSOLUTELY LEGAL! You are requesting a legitimate service and you are paying for it!! Like most of us I was a little skeptical and little worried about the legal aspects of it all. So I checked it out with the U.S. Post Office (1-800-238-5355) and they confirmed that it is indeed legal!! Mail the six envelopes to the following addresses: 1) R. Visser P.O. Box 274 Nobby Beach QLD, 4218 Australia 2) S. Phillips 77 Manly Drive Robina, QLD 4226 Australia 3) Chris Pittman 7651 Abigail Glen Dr. Charlotte, NC 28212 USA 4) D Larrinaga 609 n. tweedt #203 kennewick, WA 99336 USA 5) W Beagen 48 Brook St Methuen, Ma 01844 6) J.L. Herzfeld P.O.Box 26099 Saint Louis,MO 63136-0099 STEP TWO:Now take the #1 name off the list that you see above, move the other names up (six becomes 5, 5 becomes 4, and etc.) and add YOUR NAME as number 6 on the list. STEP THREE: Change anything you need to but try to keep this article as close to original as possible. Now post your amended article to at least 200 news groups. : (I think there are close to 24,000 groups) All you need is 200, but remember, the more you post, the more money you make!! This is perfectly legal!! If you have any doubts, refer to Title 18 Sec. 1302 & 1341 of the Postal Lottery laws. Keep a copy of these steps for yourself and whenever you need money, you can use it again, and again. PLEASE REMEMBER that this program remains successful because of the honesty and integrity of the participants and by their carefully adhering to directions. Look at it this way. If you were of integrity, the program will continue and the money that so many others have received will come your way. NOTE: You may want to retain every name and address sent to you,> either on a computer or hard copy and keep the notes people send you. This VERIFIES that you are truly providing a service. (Also, it might be a good idea to wrap the $1 bill in dark paper to reduce the risk of mail theft). So, as each post is downloaded and the directions carefully followed, all members will be reimbursed for their participation as a List Developer with one dollar each. Your name will move up the list geometrically so that when your name reaches the #1 position you will be receiving thousands of dollars in CASH!!! What an opportunity for only $6.0
Re: Smart CVS
Liquidchild wrote: > > The reason i am using locks is because the files are XML, and as far as > i know when CVS trys to merge XML it can result in invalid XML. I do > however remember on previous uses of CVS the option to check stuff out > as read only. However I cannot find that option now, this option was on > the WinCvs client I am sure. > I have not searched the net for problems with XML and CVS, but I thought XML was text, and as such should be reasonably merge-able by CVS ... that is unless your XML contains binary blobs like what MS Word kicks out. I assume then that you have either seen some problems yourself or read about it on line? > Do i require to do some sort of configuration on the Cvs Server to > allow the locking of files? I have read the above manual, well > actually the manual for 1.11.17, as this is what I am using, it just > seems to describe the difference between reserved and normal edits. > In most situations, with reasonable developers, reserved edits and watch notification, can take the place of locking. i.e., you can do `cvs watch on *XML` [1] setup the notify administrative file and have the developers do `cvs watch add -a all file_they_work_on` then have them do `cvs edit filename` anytime they need to edit a file. Then here is the hard part, if they get a notification that another user has begun editing a file, they should contact that user and negotiate with them the time needed to finish their own edits. You might also want to look at the 1.12.x series, IIRC it has the "advisory lock" patch in it, and can stop the edit from working, if there is someone else editing the file, unless the developer knowingly bypasses the edit with an option. i.e., it is a stronger (extended) form of the 'cvs watch on` + `cvs edit` commands. > I have been able to check out the repository but then had to manually > tell it to unedit all the files, so they appeared as locked. Had you already done `cvs watch on` on the files? if you had then they should have come as read-only (locked). > Then when > i commit a change to a file it just leaves it as editable, were in > previous use of cvs it would go back to being uneditable, i.e read > only. Then I would expect you had not yet done a `cvs watch on` on those files, the manual indicates [2] : "the cvs commit command, which checks in your changes and returns the watched files to their usual read-only state" > > Does anyone know if i need to do something else that I may have not > done. See above and below. :) > > Thanks all for the extended help > > S. [1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_10.html#SEC88 [2] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_10.html#SEC91 -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs branch version
> Hi, > > I used 'cvs tag' to add a file to a branch. I then used 'cvs commit > -r... ' to check in a new version. It normally creates a subversion from > the version initially tagged. For example, I tag file 'A' version 1.1 > with "release-patch". It creates a version 1.1.0.2 for the tag. When I > check in a new version to the branch, it creates a version 1.1.2.1. But > this time, I did not see any output from the command line after I > entered the comments in vi. When I did a 'cvs log', I did not see any > subversion created. > Did you change the file before committing it? CVS will not create a new revision unless there are changes from the old one. > If I do a 'cvs status' on the file, the sticky tag shows : > Sticky Tag: release-patche (branch: 1.1.2) > > But I cannot see this revision with 'cvs log'. Can anyone explain what > happened? > Sure. You now have the file in your working area as branch 1.1.2, but since there is no change from the original version, the only revision is 1.1. This revision is on both the trunk and the branch right now. That's what it looks like to me. 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 Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
The reason i am using locks is because the files are XML, and as far as i know when CVS trys to merge XML it can result in invalid XML. I do however remember on previous uses of CVS the option to check stuff out as read only. However I cannot find that option now, this option was on the WinCvs client I am sure. Do i require to do some sort of configuration on the Cvs Server to allow the locking of files? I have read the above manual, well actually the manual for 1.11.17, as this is what I am using, it just seems to describe the difference between reserved and normal edits. I have been able to check out the repository but then had to manually tell it to unedit all the files, so they appeared as locked. Then when i commit a change to a file it just leaves it as editable, were in previous use of cvs it would go back to being uneditable, i.e read only. Does anyone know if i need to do something else that I may have not done. Thanks all for the extended help S. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
