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

Re: vendor branch merge: how to highlight patches for review?

From: Q. Chap <quitechap_at_gmx.com>
Date: Thu, 30 Aug 2012 12:41:20 -0400

> > you can see which files you changed using this command:
> >
> > $ svn diff --summarize \
> > http://svn.example.com/repos/vendor/libcomplex/1.0 \
> > http://svn.example.com/repos/calc/libcomplex
>
>
> It answers the question you asked, which was:
>
> On Aug 28, 2012, at 15:57, "Q. Chap" wrote:
>
> > I'd like carefully examine the files that I've previously patched just to ensure things still make sense or are required.
>
> That is, the command I previously posted will indicate to you what files you previously patched.
> You can then merge the new version into your working copy, and carefully examine those files and
> test the project as much as you like before committing them.
>

Yes, this is nessary and valuble too.  

However, the above does not show you the patches in the context of the libcomplex-2.0 code.  (Which may have large updates, file renames/moves, etc.)
Received on 2012-08-30 19:41:17 CEST

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.