Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Date: Thu, 19 Apr 2007 11:31:54 +1000
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: Eclipse and forrest.
Message-ID: <20070419013154.GX1760@igg.indexgeo.com.au>
References: <003001c780e2$9c989cc0$650fa8c0@developer>
 <4624B05B.4080906@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4624B05B.4080906@apache.org>
User-Agent: Mutt/1.4.2.2i

Ross Gardler wrote:
> Gav.... wrote:
> >
> >2. Do you use the subclipse plugin to use SVN, if not, how do you keep
> >Eclipse upto date with trunk.
> 
> Subclipse is OK for updating from SVN, but I don't like it for 
> committing changes. It seems to get all tied up in knots far too often 
> and the GUI makes it too easy to make mistakes.
>
> I use subclipse to update and for working with diffs, but I've switched 
> back to using the command line for committing.

Yes, GUIs seem to be too dangerous.

I love the command-line for committing. I don't provide
a message. This deliberately open my text editor
where i can create/paste my message. Importantly
this enables me to simply quit the editor without
writing, which enables me to abort the commit.

It is incredible how often i use that feature.
The act of committing seems to make one think more
about the consequences.

-David