From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [ANN] mtn2git v0.1
Date: Sat, 13 Sep 2008 20:18:33 +0200 [thread overview]
Message-ID: <48CC03F9.6090505@klever.net> (raw)
In-Reply-To: <94a0d4530809131053u7c2f2c1chb33e5da39c4450aa@mail.gmail.com>
> On Sat, Sep 13, 2008 at 8:43 PM, Michael Krelin <hacker@klever.net> wrote:
>>> I did look at it, but there are some issues. For starters it seems to
>>> be using extensively the manifest, which would probably make it very
>>> slow. Also, it seems to be keeping the trees of all the revisions.
>> Back when mtn2git script was on the early stages of development and I've had
>> some time I've started doing my own mtn2git gateway in c++ (never finished
>> it, though). For what I remember using manifest was the only way, because
>> the changes information mtn automate returns was incomplete or simply wrong,
>> I don't remember the details... Do check your results carefully if you're
>> trying to go this way. Luckily, being slow due to use of manifest should
>> only matter on initial import.
>
> It's complicated, but hopefully doable.
>
> That's why there are two methods; one that does a full checkout of the
> revision and imports it into git, and the other one that uses mtn
> automate and fast-import.
>
> I'm able to import about 60% of the Pidgin code correctly, but after
> that there are issues. That's the benefit of having two modes... I can
> compare the fast one with the exact one and improve the fast one.
I ended up using some hybrid mode myself, but the point is - there's no
way to avoid pulling manifests all the time and that doesn't imply
complete checkout.
Love,
H
next prev parent reply other threads:[~2008-09-13 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 22:59 [ANN] mtn2git v0.1 Felipe Contreras
[not found] ` <m3d4j8nzy9.fsf@localhost.localdomain>
2008-09-13 10:52 ` Felipe Contreras
[not found] ` <200809131402.11413.jnareb@gmail.com>
2008-09-13 15:21 ` Felipe Contreras
2008-09-13 16:03 ` cyril Romain
2008-09-13 16:42 ` Felipe Contreras
2008-09-13 17:43 ` Michael Krelin
2008-09-13 17:53 ` Felipe Contreras
2008-09-13 18:18 ` Michael Krelin [this message]
2008-09-13 18:27 ` Felipe Contreras
2008-09-14 8:59 ` Michael Krelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48CC03F9.6090505@klever.net \
--to=hacker@klever.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox