Problems using Mercurial

[Khoo Meng Tze-B10971]

Hi Giorgos,

Thanks a million!!!
Its working now!!

Rgds,
Khoo Meng Tze

-----Original Message-----
From: Giorgos Keramidas [mailto:keramida at ceid.upatras.gr] 
Sent: Friday, April 13, 2007 3:44 PM
To: Khoo Meng Tze-B10971
Cc: mercurial at selenic.com
Subject: Re: Problems using Mercurial

On 2007-04-13 10:14, Khoo Meng Tze-B10971 <B10971 at freescale.com> wrote:
> Hi,
>  
> I'm a new user of the Mercurial system. I am trying out the system the

> first time on my pc, and got some error messages when I try to "hg ci"
> my changes on my local repository.
>  
> This were the steps that I took
>  
> -create directory on unix system (Solaris) -mv some txt files into the

> directory -run hg init on that directory (successful)
>  
> -run hg ci -A
> response:
> HG: user: MT KHOO <b10971 at freescale.com <mailto:b10971 at freescale.com> 
> >
> HG: branch default
> HG: changed x1.txt
> ~
> ~
> ~
> ~
> "/tmp/hg-editor-fBtjNQ.txt" 4 lines, 80 characters
>  
> -Ctrl-z because no response from terminal

That's where things started going downhill.  When you run "hg ci -A", an
editor fires up, where you get a chance to write a commit log entry for
the changeset you are about to create.

By hitting ^Z you sent the editor to the background.  Mercurial is still
waiting for you to write a commit log and quit from the editor.

> -run hg status
> response:
> cvsserv{b10971}116:hg status
> A x1.txt

The file is still 'modified in the workspace' and uncommitted.

Use "fg" to bring back the editor.  Write a commit log.  Save it, and
quit the editor.