Hi All,
I'm trying to set up a by-the-book vendor branch, but I need to share it with
two projects that exist in their own repositories.
The patches I need to maintain to the vendor code do need to be shared by both
projects, so that makes things simpler I think.
Here is the structure I
>> If you don't use the client side tools, how can you maintain in-house changes
>>
>> against a series of vendor drops?
>
> By following the procedure: clean drops in /vendor/foo/current, tag
> releases to /vendor/foo/N (1,2,3...). The diff between them can be merged.
> Copy current to trunk once
Hi Andreas,
>> What are the currently accepted best practices / tools for maintaining
> > "vendor" branches?
> >
> > I've seen the page at:
> > http://svnbook.red-bean.com/en/1.7/svn.advanced.vendorbr.html
> >
> > I ask about updated guidance since:
> >
> > 1) I notice some (?) churn for th
