[PATCH] status: add option to show status of files in subrepos

[Matt Mackall]

On Thu, 2010-07-08 at 15:58 +0200, Didly Bom wrote:
> On Thu, Jul 8, 2010 at 3:44 PM, Matt Mackall <mpm at selenic.com> wrote:
>         On Thu, 2010-07-08 at 15:24 +0200, Didly Bom wrote:
>         
>         > What about hg pull/push? As far as I know pull and push do
>         not
>         > currently work recursively, do they?
>         
>         
>         Push does, pull is delayed until update time. See the list
>         archives for
>         rationale.
> 
> 
> Matt, I found the following quote from you:
> 
> 
> "We don't even know what subrepos to pull until update has occurred
> because the relevant data is stored in the target changeset."
> 
> 
> If that is what you refer to, I don't quite understand it. When you
> pull you simply get new revisions from the source repository, but you
> do not change the current revision unless you later do an update.
> Thus, when you do the pull, don't you already know which subrepos are
> currently (as in the current top repository revision) are included in
> the top repository? Thus, don't you already know the list of subrepos,
> for which you could then execute a pull?
> 
> 
> I don't really understand what has "update" to do with it at all.
> Would you care to explain it further?

The information about which subrepo to pull is stored in a file
called .hgsub.

There may be many versions of that file pointing to different subrepos
in different places in many heads of many branches in the repository
you're pulling/cloning. We won't know which .hgsub version is of
interest until you decide to update.

Further, we won't have anywhere to PUT those subrepos until an update
anyway, because subrepos live in the working directory.

-- 
Mathematics is the supreme nostalgia of our time.