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

Re: Problems understanding file addition and removal after patches

From: Lukas Ruf <ruf_at_rawip.org>
Date: 2004-04-15 17:37:27 CEST

> Ben Collins-Sussman <sussman@collab.net> [2004-04-15 17:12]:
>
> On Thu, 2004-04-15 at 06:40, Lukas Ruf wrote:
> > Dear all,
> >
> > when I apply a patch to an existing directory, for example
> > upgrading linux-2.4.25 to 26, files might be added or removed.
> >
> > So far, I have figured out that I can check the status by "svn
> > status" which reports new files with '?' and removed files with
> > '!'.
> >
> > Since I must accept all the changes by the upstream patches in any
> > case, I have been wondering if there is another, smoother way to
> > handle these additions and removals than just typing all the file
> > names one after the other.
>
> You're doing the reasonable thing. Some shell scripting can help:
> pipe 'svn status' output into a script which notices '?'/'!' files
> and automatically 'svn add/rm's them. There's no reason to
> hand-type every file.
>
> Also read the section about 'vendor branches' in chapter 7; in
> particular, the svn_load_dirs.pl script might help you out here.
>

thanks for the reply!

> But honestly, if you spend lots of time trading patches with people and
> trying to manage them, you might be better off with 'arch'.
>

fortunately, the only vendor I need to keep in synch with is linux
stable. So, I am starting to be quite happy with svn....

wbr,
Lukas

-- 
Lukas Ruf           | Wanna know anything about raw |
<http://www.lpr.ch> | IP? -> <http://www.rawip.org> |
eMail Style Guide: <http://www.rawip.org/style.html>|
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Apr 15 17:38:02 2004

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.