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

List:       subclipse-dev
Subject:    Re: [Subclipse-dev] Commit Queue feature
From:       Mark Phippard <markphip () gmail ! com>
Date:       2009-11-04 12:08:22
Message-ID: ff892c5d0911040408g5851931sdd60761461ddca11 () mail ! gmail ! com
[Download RAW message or body]

What you want is called changesets.  It sounds like you are already
using the Synchronize view.  That is good, because it is a pre-req to
using this feature.  In the Synchronize view, you should be able to
select the option on the view toolbar to switch into "Changesets"
mode.  This allows you to group your changes into logical groups as
well as maintain a commit comment for each group.  You can then commit
a changeset separately from the others when you are done.

The only thing you cannot do is have two different changes to a single
file appear in two different changesets.

Mark



On Tue, Nov 3, 2009 at 8:29 PM, Edemilson Lima <pulstar@gmail.com> wrote:
> Hello!
>
> I have a suggestion about the commit feature of the Subclipse plug-in.
>
> Everytime I do a commit, the SVN generates a new version. Instead of
> generating a new version for each commit, I would like to put files and
> folders on a queue for commiting them later. In this case, when I queue a
> file or a directory, it could disappear from the synchronize list. It would
> be even better if I could choose different comments for each entry and it
> automatically group entries with the same comment. So, when I choose to
> commit, it could do different commits for each group. By this way, I could
> make a much better versioning of different file packages inside my projects.
> I know I can do this by holding the control key down and select the files I
> want to commit for each version, but when I have a lot of files to commit,
> it is very hard to select the right files and doing this way I can't use the
> compare feature to check each file. Well, I hope you got my point.
>
> Another idea was if I could choose when I want to create a new version or
> commit to the last version. This could be another way to do the same thing
> of the suggestion above, but it is not so good, and I don't know if the SVN
> protocol allows this.
>
> Best regards,
>
> Edemilson Lima
>
>



-- 
Thanks

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

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

To unsubscribe from this discussion, e-mail: [dev-unsubscribe@subclipse.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]