Where are we ...

[Lester Caine]

I need a little bit of a sanity check ...

I'm using hggit into github for single repos and things have been working nicely
in both TortoiseHg and in MercurialEclipse. ME is certainly looking good these
days and I think that I can start dropping THg as my interface to github.

The question is where ave things got to with subrepos?

git://github.com/bitweaver/bitweaver is a 'distribution' superproject, and while
the older version of hggit downloads the files from the wrapper, currently I'm
getting 'abort: No module named config!' when trying to download the same project.

Should the current build support the subrepos from git? Or is that still work in
progress. One thing which I KNEW was going to be a problem is that I'm not sure
what version IS working. It would be nice if we had some version data either in
the files, or at least in the folder. I've tried to chcek back aginst the
history but am just going around in circles :(

--
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
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

[Augie Fackler]

submodules aren't supported unless you install dulwich from their
master and hg-git from 'next'.

> --
> You received this message because you are subscribed to the Google Groups
> "hg-git" group.
> To post to this group, send email to hg-...@googlegroups.com.
> To unsubscribe from this group, send email to
> hg-git+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/hg-git?hl=en.
>

[Lester Caine]

Augie Fackler wrote:
> submodules aren't supported unless you install dulwich from their
> master and hg-git from 'next'.

OK Making progress ...
https://github.com/lsces/bitweaver is a fork of the target, and I've switched
the .gitmodule paths to give me access to the repos, but while it is building
what looks like a clean set of .hgsub and .hgsubstrate, I'm getting -
cloning subrepo articles from git://github.com/bitweaver/articles
abort: No such file or directory

I can't be far off, but what am I missing?

[Lester Caine]

Lester Caine wrote:
> Augie Fackler wrote:
>> submodules aren't supported unless you install dulwich from their
>> master and hg-git from 'next'.
>
> OK Making progress ...
> https://github.com/lsces/bitweaver is a fork of the target, and I've switched
> the .gitmodule paths to give me access to the repos, but while it is building
> what looks like a clean set of .hgsub and .hgsubstrate, I'm getting -
> cloning subrepo articles from git://github.com/bitweaver/articles
> abort: No such file or directory
>
> I can't be far off, but what am I missing?

OK I can answer my own question ... was not expecting to need git as well :)
Downloading a full clone now!

[Lester Caine]

Lester Caine wrote:
> OK I can answer my own question ... was not expecting to need git as well :)
> Downloading a full clone now!

OK what I have is looking reasonably good, but following through to TortoiseHg
and MercurialEclipse is getting confused by the .git clones in each of the
sup-repos. So what is the 'plan'?

If I drop the .hg folder from the regular clones in parallel with the .git one
I'm actually able to see all the history in MercurialEclipse and this works for
me as I have one 'project' rather than 40 and this makes life a lot easier, but
I'm still confusing things with the master superproject repo.

[Augie Fackler]

On Wed, Oct 10, 2012 at 9:24 AM, Lester Caine <les...@lsces.co.uk> wrote:
> Lester Caine wrote:
>>
>> OK I can answer my own question ... was not expecting to need git as well
>> :)
>> Downloading a full clone now!
>
>
> OK what I have is looking reasonably good, but following through to
> TortoiseHg and MercurialEclipse is getting confused by the .git clones in
> each of the sup-repos. So what is the 'plan'?

Huh? There is (by default) a .hg/git repo, but that's a bare
repository, which eclipse shouldn't get confused by?

>
> If I drop the .hg folder from the regular clones in parallel with the .git
> one I'm actually able to see all the history in MercurialEclipse and this
> works for me as I have one 'project' rather than 40 and this makes life a
> lot easier, but I'm still confusing things with the master superproject
> repo.
>
>
> --
> 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
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>

[Lester Caine]

Augie Fackler wrote:
>> OK what I have is looking reasonably good, but following through to
>> >TortoiseHg and MercurialEclipse is getting confused by the .git clones in
>> >each of the sup-repos. So what is the 'plan'?

> Huh? There is (by default) a .hg/git repo, but that's a bare
> repository, which eclipse shouldn't get confused by?

Not so much 'confused' as 'unable to display' ...
Having copied the .hg from a direct clone, refresh status on a sub-repo then
history and annotation work as they used to :)

But I did speak a little soon. The clone has processed every sub-repo in the
first level, but not in the second level. Actually I don't particularly agree
with that method anyway and in this case the two missing libraries will be
'relocated' in my own 'super-project' anyway. But is that particular problem
tagged somewhere? That is the --recursive bit on git.

Just updating TortoiseHg and Hg yet again :)