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

Re: [Subclipse-users] Patch uses absolute paths

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-05-19 21:20:10 CEST

Bradley Wagner <bradley.wagner@hannonhill.com> wrote on 05/19/2006
03:16:05 PM:

> I too have been observing this behavior in 3.1.2 all of the sudden.
> It seems to come up when you have new files in your patch which I did
> "Team->SVN add". When trying to apply the patch, the new files are
> marked with exclamation points saying that they don't currently exist
> and the modified files say the same because it's trying to use the
> whole absolute path relative to the project. The way to get around
> this for now is to "ignore leading path name segments" for as many
> directories as up to the project root. This might be only a Mac,
> Linux-based Eclipse problem.

Perhaps it is a Mac problem? I have applied patches in the past on my Mac
though. I think I was always using 3.0.2 though when doing so.

The point I made in another post is that Apply Patch is 100% Eclipse code.
 We do not run at any point in the process. If there are problems it
needs to be reported to them. Full paths being specificied in a patch is
not a problem. If you think it is, then you need to report that to the
Subversion developers and convince them to never produce a patch with svn
diff that contains full paths.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Fri May 19 21:20:19 2006

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

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