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

Re: [Subclipse-users] Retain changelists when committing

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 19 Apr 2011 17:31:55 -0400

On Tue, Apr 19, 2011 at 4:51 PM, Daniel Becroft <djcbecroft_at_gmail.com> wrote:
> On Wed, Apr 20, 2011 at 3:22 AM, Mark Phippard <markphip_at_gmail.com> wrote:
>> On Mon, Apr 18, 2011 at 8:52 PM, Daniel Becroft <djcbecroft_at_gmail.com>
>> wrote:
>> > Is there a way to keep the file's changelist assignment after a commit?
>> Just guessing ... but doesn't a file have to be locally modified to
>> even appear in a changeset?  If so, I would guess that is why the
>> changeset is gone after committing.
> That's not entirely correct. I can assign unmodified files to a changelist,
> and this file will appear as 'unmodified' in an 'svn status' command.
> The default behaviour for 'svn commit', is to remove the changelists after a
> commit. There's an option ('--keep-changelists'), that will keep the
> changelists after a commit rather than deleting them.
> Is this option available somewhere in Subclipse?

Subclipse doe not use the Subversion changelist feature. The latter
came 3-4 years after Subclipse added this feature and it does not
support all the capabilities of Eclipse change sets. So I was talking
about the behavior of Eclipse change sets which were introduced with
Eclipse 3.0.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-04-19 23:31:57 CEST

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.