Send info-cvs mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.nongnu.org/mailman/listinfo/info-cvs
or, via email, send a message with subject or body 'help' to
address@hidden
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of info-cvs digest..."
Today's Topics:
1. Re: Please read - Need help with sticky tag (michael)
2. Help: Protocol error: too many arguments (An Qin)
3. emailing the logs to all CVS users (Awadh Bajpai)
4. Re: emailing the logs to all CVS users (Larry Jones)
5. Re: Help: Protocol error: too many arguments (Spiro Trikaliotis)
6. Branching strategy question (Tim Velten)
----------------------------------------------------------------------
Message: 1
Date: 15 May 2007 02:58:50 -0700
From: michael <address@hidden>
Subject: Re: Please read - Need help with sticky tag
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"
Hello Dennis,
thank you very much for reading and answering as much as for the
advice.
I finally solved the problem.
As I allready thought the same about moving to tortoise I will now do
so.
Even if I appreciate the effort by the WinCVS programmers, it is
definately not intuitive.
Regards,
Michael
Dennis Jones schrieb:
"michael" <address@hidden> wrote in message
news:address@hidden
> Hello,
>
> I must confess, I already wrote a message considering the sticky
> issue.
> But unfortunately without any answer.
>
> I allready read the threads mentioning sticky tag, but all solutions I
> found where not applicable to my situation. Please read on and if you
> have any hint, please let me know.
>
> I now reconstructed the way I got into that trap.
>
> 1. I was working on my own on a branch of my project.
> 2. Modified a file, but wanted to get back the last revision (from the
> branch) I commited.
> 3. Used first Update from the main menu (WinCVS). This does not help.
> 4. Used Update (sticky) from the graph menu.
> 5. Modified and wanted to commit then.
> 6. It says that sticky tag is not a branch.
My guess is that (in step 4 above) you updated based on a revision number (I
think that's what you end up getting if you do an update using the graphical
display in WinCVS, but I don't use WinCVS so I can't be certain). Anyway,
what you need to do is update using the branch tag instead of a revision
number, which will give you a sticky tag that is associated with the branch
you are currently working on (though you do have to know the name of the
branch):
cvs up -r<branch_tag> <filename>
for example:
cvs up -r MY_BRANCH myfile.cpp
As to how you got yourself into this mess: if I understand you correctly,
what you wanted to do was get a clean copy of the file you were working on.
In other words, you wanted to lose any changes you had made and start over.
To do this, you would need to use the "get a clean copy" flag with the
update command. I don't know how you would do that in WinCVS, but from the
command line, it is simple:
cvs up -C myfile.cpp
This will give you the latest revision of myfile.cpp on the current branch
based on the file's sticky tag. This is essentially the same as deleting
the file and then doing an update (except it is done in one step and your
modified file is kept around as a backup in case you need it).
If you don't mind a piece of advice -- get rid of WinCVS and switch to
either TortoiseCVS or just use the command line CVS tool. My experience
with WinCVS was not a pleasant one, and everybody I know that has used it
has had various problems with it. Personally, I use command line CVS most
of the time, but I sometimes use TortoiseCVS which I like because it
integrates nicely into Explorer and makes using graphic diff'ing tools very
easy.
- Dennis
------------------------------
Message: 2
Date: Tue, 15 May 2007 23:47:28 +0800
From: "An Qin" <address@hidden>
Subject: Help: Protocol error: too many arguments
To: <address@hidden>
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="us-ascii"
Hi,
When I commit a large directory, I am continuously getting error message
"Protocol error: too many arguments", even though I commit everything
separately in each sub-directory. Could you please help me to figure out
the reason?
My client is Concurrent Versions System (CVS) 1.11.5.1 (client) on
WinXP.
Server is oncurrent Versions System (CVS) 1.11.17 (client/server) on
Linux.
Thank you in advance!
Qin An.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/info-cvs/attachments/20070515/011ca70e/attachment.html
------------------------------
Message: 3
Date: Tue, 15 May 2007 11:15:54 +0530
From: Awadh Bajpai <address@hidden>
Subject: emailing the logs to all CVS users
To: address@hidden
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="us-ascii"
Hi ,
I want to trigger email to all cvs server users when ever there is commit
to CVS repository.
What files & their path and what modifications to these files will
require to do so.
Please , reply if anybody is using this facility.
Thanks
Awadh Bajpai
Sr. Software Engineer, Datacom Engineering
A R I C E N T
480, Anna Salai, Nandanam
Chennai-600035
Main +0 442.433.0550
Mobile +0 984.085.7457
*********************** Aricent-Private ***********************
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of
the individual to whom it is addressed. It may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended. If you have received this message in error,
please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly
prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for
loss or damage arising from the use of the information transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/info-cvs/attachments/20070515/41b929bf/attachment.html
------------------------------
Message: 4
Date: Tue, 15 May 2007 13:44:35 -0400 (EDT)
From: address@hidden (Larry Jones)
Subject: Re: emailing the logs to all CVS users
To: address@hidden (Awadh Bajpai)
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Awadh Bajpai writes:
I want to trigger email to all cvs server users when ever there is commit
to CVS repository.
What files & their path and what modifications to these files will
require to do so.
Please read the manual:
<http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_18.html#SEC175>
There are some scripts in the contrib directory that you may find
useful, particularly log, commit_prep, and log_accum.
-Larry Jones
Ever notice how tense grown-ups get when they're recreating? -- Calvin
------------------------------
Message: 5
Date: Tue, 15 May 2007 20:13:38 +0200
From: Spiro Trikaliotis <address@hidden>
Subject: Re: Help: Protocol error: too many arguments
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Hello,
* On Tue, May 15, 2007 at 11:47:28PM +0800 An Qin wrote:
My client is Concurrent Versions System (CVS) 1.11.5.1 (client) on
WinXP.
Wow, this version is really *ancient*. I believe not even Debian Woody
used a version that old.
I would highly recommend you upgrade to a newer version and try it
again. Note, however, that I do not know if any problem like this has
been handled in between.
Server is oncurrent Versions System (CVS) 1.11.17 (client/server) on
Linux.
Well, considering that there were some security bugs, you might consider
upgrading that one, too.
Best regards,
Spiro.
--
Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/
------------------------------
Message: 6
Date: Tue, 15 May 2007 14:44:42 -0400
From: Tim Velten <address@hidden>
Subject: Branching strategy question
To: address@hidden
Message-ID:
<address@hidden>
Content-Type: text/plain; charset="us-ascii"
Hi,
We do all development on branches. The trunk represents the code that is
currently in production. All doc I read is based on development going on
in the trunk, but I don't see how that can work when there are always 2 or
3 releases in progress at any one time.
Each branch is merged into the following branch on a regular basis.
So for example, we have an April patch branch, a June branch, and an
August branch in progress. At certain points we merge April patch branch
into June branch and June branch into August branch.
When we create the October branch, it is created from the trunk and then
August branch will be merged into October branch.
So here is my question ...
When I create October branch I know that it should look exactly like
August. So if I created October branch from August branch instead of the
trunk I would eliminate the August to October merge. But then that
implies that December branch would be created from October, etc ... and
that does not seem right.
So should I stick with the original strategy and always branch off of the
trunk ?
Thanks,
Tim Velten
IBM Global Services
859 635 1785
address@hidden
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.gnu.org/pipermail/info-cvs/attachments/20070515/ff7aee10/attachment.html
------------------------------
_______________________________________________
info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs
End of info-cvs Digest, Vol 54, Issue 11
****************************************