Lemke, Michael IZ/HZA-IOP <[EMAIL PROTECTED]> wrote:
> When I do a cvs import of a new vendor version the new files become the
> head revision. I'd like to do the import such that it doesn't affect HEAD.
> Only after I've tested the new stuff I want it to become HEAD. Of course,
> it should work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lemke, Michael IZ/HZA-IOP <[EMAIL PROTECTED]> writes:
> However, this whole thing makes me realize I
> don't really understand vendor branches. What's
> different from ordinary ones?
The vendor branch more closely models the RCS
branching model. Th
> From: Mark D. Baushke
> Sent: Thursday, July 22, 2004 5:16 PM
> To: Lemke, Michael IZ/HZA-IOP
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: Import question
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Lemke, Michael IZ/HZA-IOP writes:
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lemke, Michael IZ/HZA-IOP <[EMAIL PROTECTED]> writes:
> When I do a cvs import of a new vendor version the new files become the
> head revision. I'd like to do the import such that it doesn't affect HEAD.
> Only after I've tested the new stuff I wan
> -Original Message-
> From: Christopher.Fouts
> Sent: Thursday, July 22, 2004 4:43 PM
> Subject: RE: Import question
>
> Can you "export" (not check out) the latest files you need
> from a current vendor branch, which should contain the changes
> yo
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>] On Behalf Of Lemke, Michael IZ/HZA-IOP
>Sent: Thursday, July 22, 2004 10:36 AM
>To: [EMAIL PROTECTED]
>Subject: RE: Import question
>
>
>> From: Christopher.Fouts
>> Sent: Thursday, July 22, 2004 4:22 PM
>>
> From: Christopher.Fouts
> Sent: Thursday, July 22, 2004 4:22 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Import question
>
>
> Test BEFORE importing!
Sure but I need the merge of the local changes. But I can't get them
without the import or can I?
>
>
>
Test BEFORE importing!
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>] On Behalf Of Larry Jones
>Sent: Thursday, July 22, 2004 10:12 AM
>To: Lemke,Michael IZ/HZA-IOP
>Cc: '[EMAIL PROTECTED]'
>Subject: Re: Import question
>
> -Original Message-
> From: lawrence.jones
> Sent: Thursday, July 22, 2004 4:12 PM
> Cc: [EMAIL PROTECTED]
> Subject: Re: Import question
>
>
> Lemke, Michael IZ/HZA-IOP writes:
> >
> > When I do a cvs import of a new vendor version the new
> f
Lemke, Michael IZ/HZA-IOP writes:
>
> When I do a cvs import of a new vendor version the new files become the
> head revision. I'd like to do the import such that it doesn't affect HEAD.
> Only after I've tested the new stuff I want it to become HEAD. Of course,
> it should work with local chan
I had same problem some time back but don't have any solution to it..
you can go through
http://lists.gnu.org/archive/html/info-cvs/2004-02/msg00077.html
-Rohan
Lemke, Michael IZ/HZA-IOP wrote:
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do th
When I do a cvs import of a new vendor version the new files become the
head revision. I'd like to do the import such that it doesn't affect HEAD.
Only after I've tested the new stuff I want it to become HEAD. Of course,
it should work with local changes merged in just like the standard way of
do
Am Fri, 21 Sep 2001 15:56:57 +1000 schrieb Ellison, Martin [IT]:
> Maybe distribute your property files in a build script. Then you can
keep
> them together somewhere central.
>
Good Idea, but I wouldn't think our Windows peaple are able to handle
build scripts.
Make ? What is make ? Uuh ugl
Maybe distribute your property files in a build script. Then you can keep
them together somewhere central.
> A Project in a subdir (I hope. we'll see...)
> Some property-files concerning that project wildly scattered over the
> system which should be updated etc together with the Project
> Some J
Hi !
I use cvs for some projects I'm in, but they were all quite simple. I.e.
everything was located in one subdir. Now I have to set up the following
scenario:
A Project in a subdir (I hope. we'll see...)
Some property-files concerning that project wildly scattered over the
system which should
15 matches
Mail list logo