[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subclipse-users
Subject:    Re: [Subclipse-users] Retain changelists when committing
From:       Mark Phippard <markphip () gmail ! com>
Date:       2011-04-19 21:31:55
Message-ID: BANLkTinj3NFCN8t-VjQ0R5bPfOHewhPeFg () mail ! gmail ! com
[Download RAW message or body]

On Tue, Apr 19, 2011 at 4:51 PM, Daniel Becroft <djcbecroft@gmail.com> wrote:
> On Wed, Apr 20, 2011 at 3:22 AM, Mark Phippard <markphip@gmail.com> wrote:
>>
>> On Mon, Apr 18, 2011 at 8:52 PM, Daniel Becroft <djcbecroft@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.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2721559

To unsubscribe from this discussion, e-mail: [users-unsubscribe@subclipse.tigris.org].

[prev in list] [next in list] [prev in thread] [next in thread]