Brock Janiczak <firstname.lastname@example.org> wrote on 05/21/2006 06:31:42 AM:
> Eugene Kuleshov wrote:
> > As I understood it is specific for Eclipse 3.2. I wonder what
> > options do we have in order to see this stuff in official Subversion
> > releases?
> Mark would have to make the call on this one. I tried using fragments
> and version dependent features, but that required using massive amounts
> of reflection. It looks like the only option is to branch off a new
> version (1.2 or something) and keep both branches up to date, but the
> 3.1 version will be the main focus for development.
If this feature, and possibly the History change, are finished. What I
would probably do is turn trunk development into 3.2. Then the only
question is whether it would be worth having a release line specifically
for 3.1. I think there are a few nice changes in trunk that are not in
the 1.0.x branch, but I am not sure if they would justify their own
release. We could possibly create a release specifically for 3.1 and add
in Outgoing Change Set support based on 3.1. We already have a patch that
In either event, we would just backport select features to the 1.0.x and
possibly 3.1 branch as needed. But these would mostly just be stable,
> > Hmm, can't you just use incoming revisions? In other words, if sync
> > view is in incoming mode, then just run svn log on project, get
> > affected paths for each revision and filter out resources outside of
> > the project.
> yep, that appears to work. I do have one question though, as i don't
> use SVN on a regular basis. When you check in a file, the global
> version number is incremented and the version and last changed revision
> is updated on the file. Is the 'current' version of all of the files in
> the working copy also updated to this new version number, or do you have
> to svn update them?
When a file is committed, nothing but that file is updated. Not even the
folder that contains the file. When you run svn update, it will update
the Revision to whatever you updated to (HEAD). The Last Changed Revision
lets you know the last time that file was changed.
> If you do have to run the update, how can we know
> over which revision range we need to run the log command?
Honestly, when I look at this feature in CVS, I still have no idea what it
does or what it is trying to tell me. So I have no idea what supporting
it would mean for Subverison. In other words, sorry, I cannot answer.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun May 21 20:50:05 2006