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

Re: [Subclipse-users] [Subclipse-dev] Edit while commit

From: Mark Phippard <markphip_at_gmail.com>
Date: Wed, 15 Dec 2010 09:54:41 -0500

On Wed, Dec 15, 2010 at 9:48 AM, Andreas Haferburg
<haferbur_at_inf.fu-berlin.de> wrote:
> On 12/15/2010 11:08 AM, Mikhail Barg wrote:
>> On 14.12.2010 20:57, Stephen Elsemore wrote:
>>> Since it is easy to use the Synchronize view to see which resources are
>>> ready to be committed, and to perform editable compares on those resources
>>> if necessary prior to committing, my feeling is that it's not worth changing
>>> the commit dialog.
> The unique feature of the Commit dialog is the editor for the commit
> message. Obviously I'd like to use this editor to compose the commit
> message. While composing the commit message I basically explain my
> changes to someone else, and while doing that I often notice that I
> should put similar explanations in the code as well.
> Here's how I normally work:
> - synchronize
> - select files to commit
> - open commit dialog
> - go through all the changes while adding items to the commit message
> - click ok
> I can't do that in Synchronize view because I can't compose the commit
> message there. But if I want to edit something I have to close the
> Commit dialog, and afterwards select the files to commit again, reopen
> the dialog, then continue composing the commit message. I usually open
> the file from the Synch View, which also means that I lose the selection
> of the files to commit.

Here is something you can try ... in the Synchronize view switch to
Change Sets mode and organize your changes into a change set. The
Change Set has a commit message associated with it that you can edit
and work on as you code. The dialog for this message is even modeless
so that you can have it open while writing code or viewing compares in
the synch view.

This message is just stored locally with the change set and is used to
populate the message in the commit dialog when you commit the change
set. Even if you always just have a single active change set, this
could be useful for your workflow. Obviously the feature becomes even
more useful if it is common for you to have more than one set of
changes happening in your workspace at the same time.

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2010-12-15 15:54:55 CET

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.