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

Re: Converting a revision to a patch

From: Chuck Holzwarth <chuck_holzwarth_at_yahoo.com>
Date: Fri, 6 Mar 2009 13:52:25 -0800 (PST)

How about creating a branch and checking the non subversion code in, check it out, merge the code you want to the branch and do the patch from there?

 Thank you,
Chuck Holzwarth

________________________________
From: Mark Wagner <carnildo_at_gmail.com>
To: Nathan Nobbe <quickshiftin_at_gmail.com>
Cc: users_at_subversion.tigris.org
Sent: Thursday, March 5, 2009 8:35:37 PM
Subject: Re: Converting a revision to a patch

On Thu, Mar 5, 2009 at 17:20, Nathan Nobbe <quickshiftin_at_gmail.com> wrote:
>
> On Thu, Mar 5, 2009 at 5:30 PM, Mark Wagner <carnildo_at_gmail.com> wrote:
>>
>> I've got a Subversion repository containing a set of changes I'm
>> interested in (specifically, revision 189) and a version of the source
>> code that isn't managed by Subversion. How would I go about
>> converting r189 into a patch to apply to the non-managed code, or is
>
> svn diff -c 189 $pathToUrl
>
> then use that to patch. at least i think that should do it..

Thanks.

>> there a better way to do this?
>
> version everything.

Got a time machine?

-- 
Mark Wagner
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1274815
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1279151
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-06 22:53: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.