something wrong with status command

Wagner Bruna wagner.bruna+mercurial at gmail.com
Fri Nov 26 16:02:53 UTC 2010


On 11/26/2010 01:16 PM, Marco Giovannini wrote:
> I think the file shouldn't be 'A' after a pull right ?
> 
> C:\Documents and Settings\GiovannM\Desktop\cloned>hg status -S
> 
> C:\Documents and Settings\GiovannM\Desktop\cloned>hg onsub "hg pull"
> pulling from c:\Documents and Settings\GiovannM\Desktop\main\../sub1
> searching for changes
> no changes found
> pulling from c:\Documents and Settings\GiovannM\Desktop\main\../sub1\../sub2
> searching for changes
> adding changesets
> adding manifests
> adding file changes
> added 1 changesets with 1 changes to 1 files
> (run 'hg update' to get a working copy)

What happens if you run "hg status -S" *at this point*?

> C:\Documents and Settings\GiovannM\Desktop\cloned>hg onsub "hg update"
> 0 files updated, 0 files merged, 0 files removed, 0 files unresolved
> 1 files updated, 0 files merged, 0 files removed, 0 files unresolved

  ^ Here the update command is telling you that one file has changed
inside a subrepo, so it'd be pretty surprising if status didn't show
any changes right after this!

But note that, regardless of file changes, changing the working copy
revision of a subrepo will always change its state from the main repo
point of view.

Hope that helps,
Wagner

> C:\Documents and Settings\GiovannM\Desktop\cloned>hg status -S
> A sub1\sub2\sub2_file01
> 
> Regards,
> Marco



More information about the Mercurial mailing list