Old OE history

Old OE history

[Paul Eggleton]

Hi there,

Looking back through OE-Classic git commit history, the first commit (from 
Chris) is basically an import; so it seems to me that at one point we did have 
some more history from before then. This was before my time on the project so 
I'm not sure what we had before bitkeeper (if anything).

Does anyone actually have this early history saved somewhere?

Cheers,
Paul
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

Re: Old OE history

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Eggleton schreef op 09-06-14 19:34:
> Hi there,
> 
> Looking back through OE-Classic git commit history, the first commit
> (from Chris) is basically an import; so it seems to me that at one point
> we did have some more history from before then. This was before my time
> on the project so I'm not sure what we had before bitkeeper (if
> anything).

We had CVS, but IIRC Chris imported that into bitkeeper.

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFTlquNMkyGM64RGpERAprXAJ9KppyuXnKARIBNR8ATS7fo7bouJQCfcWss
7HCddK/u5r++0G4yqpDg+sk=
=yL7V
-----END PGP SIGNATURE-----

Re: Old OE history

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Koen Kooi schreef op 10-06-14 08:54:
> Paul Eggleton schreef op 09-06-14 19:34:
>> Hi there,
> 
>> Looking back through OE-Classic git commit history, the first commit 
>> (from Chris) is basically an import; so it seems to me that at one
>> point we did have some more history from before then. This was before
>> my time on the project so I'm not sure what we had before bitkeeper
>> (if anything).
> 
> We had CVS, but IIRC Chris imported that into bitkeeper.

Judging from the commits
https://github.com/openembedded/openembedded/commits/master?page=1561 it
looks like the import from hh.org cvs is there, but I guess we're missing
the sourceforge bits (if those exist). The OZ buildroot based cvs is still
up on sf.net.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFTlq28MkyGM64RGpERAppJAKCgYQehWDcf2Ir9DFYIbm5t5Iv9rACfZTjx
2lapaFhE9i5ixh6l+HyClR4=
=d1EO
-----END PGP SIGNATURE-----

Re: Old OE history

[Christopher Larson]

On Mon, Jun 9, 2014 at 10:34 AM, Paul Eggleton <paul.eggleton@intel.com>
wrote:

> Looking back through OE-Classic git commit history, the first commit (from
> Chris) is basically an import; so it seems to me that at one point we did
> have
> some more history from before then. This was before my time on the
> project so
> I'm not sure what we had before bitkeeper (if anything).
>

This doesn't seem accurate to me. The first commit is
bda361cba6cf49d92d21f44c87a9d2f13511d551, which created an initial mostly
empty repository, which was followed by
c11afe579262bdabdf3af8fdfcb24b3598bf0232 which added a couple initial
recipes, etc.

At one point we used cvs, which got imported into bk, which got re-exported
as cvs, which got imported into mtn, which got converted to git, or
something like that, if I'm remembering correctly, anyway :) And of course
I did some careful grafting of the earliest histories. I'm pretty sure we
have most of the historical repositories around somewhere or another. I
know I have copies of the bkbits repository for bitbake, the oz buildroot
repo from various places, and  the cvs exports of the bkbits repositories.
It is of course possible that something got lost in the translations
between scm types along the way, but I'm not aware of anything missing
offhand. And of course the initial repository was prior to bitbake being
split out, the split of the early history between bitbake and openembedded
was done by me, as carefully as I could, but iirc we still have the old
'oe' repository which was prior to the split.

If I dump a list of every file which has ever existed in the oe classic
repository, and then grep out qt.*/compile.patch from that, and use git log
on those files, you can see all the way back to the import of the initial
qt/qte patches from the oz buildroot, and subsequent changes to it after
that:

    git log -- (git rev-list --reverse HEAD | git diff-tree --stdin
--no-commit-id --name-only -r | sort -u | grep 'qt.*/compile.patch')

Aside: I have 'git rev-list --reverse HEAD | git diff-tree --stdin
--no-commit-id --name-only -r | sort -u' as a standalone git-ls-files-ever
script. this is particularly useful when splitting git repositories up, or
doing complete svn to git conversions, to ensure that you don't miss any
files, as git's --follow isn't always sufficient, nor are other uses of its
copy/move detection.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics

Re: Old OE history

[Paul Eggleton]

On Tuesday 10 June 2014 20:19:53 Christopher Larson wrote:
> On Mon, Jun 9, 2014 at 10:34 AM, Paul Eggleton <paul.eggleton@intel.com>
> wrote:
> > Looking back through OE-Classic git commit history, the first commit (from
> > Chris) is basically an import; so it seems to me that at one point we did
> > have
> > some more history from before then. This was before my time on the
> > project so
> > I'm not sure what we had before bitkeeper (if anything).
> 
> This doesn't seem accurate to me. The first commit is
> bda361cba6cf49d92d21f44c87a9d2f13511d551, which created an initial mostly
> empty repository, which was followed by
> c11afe579262bdabdf3af8fdfcb24b3598bf0232 which added a couple initial
> recipes, etc.
> 
> At one point we used cvs, which got imported into bk, which got re-exported
> as cvs, which got imported into mtn, which got converted to git, or
> something like that, if I'm remembering correctly, anyway :) And of course
> I did some careful grafting of the earliest histories. I'm pretty sure we
> have most of the historical repositories around somewhere or another. I
> know I have copies of the bkbits repository for bitbake, the oz buildroot
> repo from various places, and  the cvs exports of the bkbits repositories.
> It is of course possible that something got lost in the translations
> between scm types along the way, but I'm not aware of anything missing
> offhand. And of course the initial repository was prior to bitbake being
> split out, the split of the early history between bitbake and openembedded
> was done by me, as carefully as I could, but iirc we still have the old
> 'oe' repository which was prior to the split.
> 
> If I dump a list of every file which has ever existed in the oe classic
> repository, and then grep out qt.*/compile.patch from that, and use git log
> on those files, you can see all the way back to the import of the initial
> qt/qte patches from the oz buildroot, and subsequent changes to it after
> that:
> 
>     git log -- (git rev-list --reverse HEAD | git diff-tree --stdin
> --no-commit-id --name-only -r | sort -u | grep 'qt.*/compile.patch')
> 
> Aside: I have 'git rev-list --reverse HEAD | git diff-tree --stdin
> --no-commit-id --name-only -r | sort -u' as a standalone git-ls-files-ever
> script. this is particularly useful when splitting git repositories up, or
> doing complete svn to git conversions, to ensure that you don't miss any
> files, as git's --follow isn't always sufficient, nor are other uses of its
> copy/move detection.

Ah, thanks for this - this works a lot better. However, I think the reason 
that I was getting confused before is that some of the patch files I'm trying 
to trace appear to start with zero size in the history, which leads git's 
rename detection with --follow down the wrong path. I'd also missed that some 
of the BK merge commits actually have useful information about the commits 
they contained; if you know what you're looking for you can match them up with 
the file(s) they refer to.

Cheers,
Paul
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.