nsolidated-tag module
[sanity check]
cvs commit -m 'blah' module
Thanks..
Euan
-Original Message-
From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
Sent: 30 March 2005 17:20
To: 'Euan Guttridge'; Jim.Hyslop; info-cvs@gnu.org
Subject: RE: Checkout's over checkouts.
Euan
Euan Guttridge wrote:
> The problem with doing that, which in fact also applies to my (bad)
> suggestion, is that this will 'schedule for removal' all
> files in HEAD not
> in tag1.
Oh, right, missed that. You still don't need the extra tags and branches
though:
cvs rtag -rtag1 consolidated-tag m
Jim.Hyslop; info-cvs@gnu.org
Subject: RE: Checkout's over checkouts.
Euan Guttridge wrote:
> I will use the consolidated tag to replace HEAD
> ( cvs up -r HEAD -j HEAD -j consolidated-tag module )
That makes it even simpler. You don't need all those extra branches and
merges. Just:
cvs
Euan Guttridge wrote:
> I will use the consolidated tag to replace HEAD
> ( cvs up -r HEAD -j HEAD -j consolidated-tag module )
That makes it even simpler. You don't need all those extra branches and
merges. Just:
cvs update -A
(make sure you have no un-committed changes)
cvs update -jHEAD -jtag1
Hi Jim
I will use the consolidated tag to replace HEAD
( cvs up -r HEAD -j HEAD -j consolidated-tag module )
Euan
-Original Message-
From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
Sent: 30 March 2005 16:28
To: 'Euan Guttridge'; info-cvs@gnu.org
Subject: RE: Checkout's
Euan Guttridge wrote:
> The best I can think of using CVS is to combine branch + tag1 as tagA,
> combine tagA with tag2 as tagB, combine tagB with tag3 as tagC etc..
Sorry, one question I forgot to ask - once you have this consolidated tag,
what will you do with it? Will you be doing further develo
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Jim.Hyslop
Sent: 29 March 2005 17:59
To: info-cvs@gnu.org
Subject: RE: Checkout's over checkouts.
Euan Guttridge wrote:
> Thanks for the input Jim and Rick, to clarify
>
> Objective:
> - check out a branch to workspa
Euan Guttridge wrote:
> [EUAN] A number of files will have the same tag, i.e. if you
> check out tag1
> you will get 20 files. This will be done weekly.
OK, now let's back up a step. Why are you doing this? What are you trying to
accomplish with this procedure?
--
Jim Hyslop
Senior Software Des
On Tue, 29 Mar 2005 18:08:15 +0100, Euan Guttridge
<[EMAIL PROTECTED]> wrote:
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> Jim.Hyslop
> Sent: 29 March 2005 17:59
> To: info-cvs@gnu.org
> Subject: RE: Che
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Jim.Hyslop
Sent: 29 March 2005 17:59
To: info-cvs@gnu.org
Subject: RE: Checkout's over checkouts.
Euan Guttridge wrote:
> Thanks for the input Jim and Rick, to clarify
>
> Objective:
> - c
Euan Guttridge wrote:
> Thanks for the input Jim and Rick, to clarify
>
> Objective:
> - check out a branch to workspace
> - *overwrite* a number of those files in workspace from
> various tags (not
> update so there is no possibility of merge conflicts)
> - tag the consolidated workspace
>
> Ca
es by name (too many)
- I will use two or more tag sets (of potentially 20 + files each)
Thanks
Euan
-Original Message-
From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
Sent: 29 March 2005 17:34
To: 'Rick Genter'; Jim.Hyslop; Euan Guttridge; info-cvs@gnu.org
Subject: RE: Checkout
> -Original Message-
> From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 29, 2005 11:34 AM
> To: Rick Genter; Jim.Hyslop; Euan Guttridge; info-cvs@gnu.org
> Subject: RE: Checkout's over checkouts.
>
> If I understand the original message correc
Rick Genter wrote:
> > From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
> > That will not replace the files, just apply a sticky tag to your
> working
> > directory.
> You're right, of course. The last command should be
>
> cvs up -rtag file1 file2 ... fileN
Same effect.
If I understand the original
I wrote:
> Euan Guttridge wrote:
> > I want to check out a branch, then subsequent tagged files on
> > top of that
> > branch. I do not want to -j merge the subsequent tagged
> files into the
> > branch but do a wholesale replacement. What is the best
> method please?
> Actually, a -j would do t
> -Original Message-
> From: Jim.Hyslop [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 29, 2005 9:37 AM
> To: Rick Genter; Euan Guttridge; info-cvs@gnu.org
> Subject: RE: Checkout's over checkouts.
>
> Rick Genter wrote:
> > [mailto:[EMAIL PROTECTED]
Rick Genter wrote:
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Euan Guttridge
> > Sent: Tuesday, March 29, 2005 6:29 AM
> > To: 'info-cvs@gnu.org'
> > Subject: Checkout's over checkouts.
> >
> > I want to check out a branch, then subsequent tagged files on top of
> that
> > branch. I do not want to
Euan Guttridge wrote:
> I want to check out a branch, then subsequent tagged files on
> top of that
> branch. I do not want to -j merge the subsequent tagged files into the
> branch but do a wholesale replacement. What is the best method please?
Actually, a -j would do the job:
cvs update -A
[mak
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Euan Guttridge
> Sent: Tuesday, March 29, 2005 6:29 AM
> To: 'info-cvs@gnu.org'
> Subject: Checkout's over checkouts.
>
> I want to check out a branch, then subsequent tagged files on top of
that
> branch
19 matches
Mail list logo