"staging area"?

[Lester Caine]

Benoit Boissinot wrote:
> On Sun, Jun 20, 2010 at 10:49 AM, Daniel Carrera<dcarrera at gmail.com>  wrote:
>> Hello,
>>
>> In Git you always have to "add" a file before committing, even if you
>> already added it before. This is their notion of a "staging area". Can
>> someone confirm that Hg does *not* work like this? In Hg, as in most
>> other SCMs, you just type "hg commit" and Hg automatically makes a
>> revision with all the changes.
>>
>> I tested, and Hg seems to work the way I think it works. I just want
>> to confirm. Thanks.
>
> That's correct, you don't have to stage changes before committing. Hg
> will commit everything shown by hg diff or hg status.

Of cause there are plusses and minuses to everything ... I've been pushed from 
CVS to GIT by one of my main projects, but I'm working with their new repo via 
hg on Eclipse and on the whole things are OK, BUT the ONE thing that I miss in 
both git and hg is the 'staging area' provided by Eclipse for CVS where I can 
see files I've updates, compare with the 'HEAD' if I need to, and select the 
files I want to commit with their own commit message. Pulling the other way is 
equally painful nowadays, the 'Team Sync' page lists the files I need to look at 
before I add them to my copy locally so I can correct obvious mistakes or leave 
a file until I'm ready to handle it.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php