On Wed, Apr 20, 2011 at 7:31 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Tue, Apr 19, 2011 at 4:51 PM, Daniel Becroft <djcbecroft_at_gmail.com>
> > On Wed, Apr 20, 2011 at 3:22 AM, Mark Phippard <markphip_at_gmail.com>
> >> 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
> >> 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
> > 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.
Ah, gotcha. Do you have any idea if this ability is coming in Eclipse at
all? It's a real pain to have to continually add files to a change set
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-05-05 07:29:49 CEST