Mark Phippard schrieb:
>
>>
>> Does anybody already had similar problems and got a solution for this?
>> Has anybody a suggestion of how a copy/branch/tag workflow has to be when we want to work a little bit like CC?
>>
>
>
> I think you would need to do something like this:
>
> 1) When you have customer mods to make, create a branch by copying
> trunk (or a release branch).
> 2) Make customizations on this branch and give to customer.
>
> A new release comes out, and you need to update the customer branch.
> The easiest way to do this would be:
>
> 1) Create new customer branch from new release branch
> 2) Merge changes from previous customer branch to the new customer branch
>
> Because the number of customizations is much smaller than the number
> of changes between releases, this is the easier way to do it
>
> I am sure it will not be as easy to do as ClearCase, but it should be
> manageable. You might also maintain a patch for each customers
> customizations so that you can just apply that to a release branch as
> needed.
>
how can I create something you called "patch". I know the patch thing
which is in unix a way to apply changes to a file set. Is there
something with subversion support as well? The only thing what I need is
identifying file revisions deltas from a base revision to a newer
revision and the same file revision again on another branch (or tag).
--
mit freundlichen Grüßen,
Joachim Armbruster
Received on 2008-02-18 20:57:35 CET