[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best way to maintain patches to a 3rd party library?

From: NN Ott <nonot100_at_gmail.com>
Date: Thu, 6 Jan 2011 19:17:33 -0500

>
>
>
>> Can I make a local (patched) branch of an svn:external? That way I could
>>> pull updates as needed, but still retain access to the full commit
>>> history.
>>>
>>
>> You'd need to manually (or some automated fashion) apply each commit
>> made to their repository to your own repository.
>> This is very tedious if they make a lot of commits.
>> And revision numbers between repositories wouldn't match up.
>>
>> I don't understand what the real problem you want to solve is.
>> Maybe you want to browse their history without internet access?
>> If you want to browse their history without internet access, I would
>> recommend keeping an svnsync copy of their repository on your hard drive.
>>
>
> I think the idea is that he'd like to see the development history of both
> the vendor and local changes as a continuous set of changes as you would if
> they were in the same repository with log and diff working across any points
> in time or branch versions. It seems like a reasonable thing to want, but I
> don't think it is possible with subversion.
>
>
>
That's exactly right.

Should I post this to the dev list?
Received on 2011-01-07 01:18:11 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.