[oe] Git Migration Status

[Rod Whitby]

Richard Purdie wrote:
> I'm going to skip the rest of your argument, I don't agree the other
> bits but this bit did does lead to something important: 

Yeah, if we couldn't convince each other in an hour of IRC discussion, 
then we're not going to do so via email.

> Say I have some tree outside OE and I commit things to is as a developer
> with no access to OE directly. "We" then want to merge that into OE.
> Even assuming the commit hooks allow this (there are ways and means) we
> immediately lose our namespace protection. There are 101 other scenarios
> that would allow this to happen and they show that namespace protection
> is pointless with git.

Agreed.

> Note that your AUTHORS file would also break with this approach unless
> at merge time you grep the external tree for all email addresses and
> then add them which would be tedious at best.

Yes, I thought it would only check the final committer, but others have 
pointed out that it checks each one in the imported tree.  So I withdraw 
that proposal.

> I think we've lost sight of the original problems so lets go back to
> them:
> 
> The points I had in mind with this was to:
> 
> a) stop insane IDs entering the repository (ich at 1.2.3.4)

Agreed.

> b) gain something we could feed into the final mtn -> git and bkcvs -> 
>    git conversions which would make more sense of the data. 
>    "crofton at openembedded.org" really isn't a useful identifier.

I agree with your proposed solution on this one.

> c) ensure we have accurate records about our committers on the wiki

I agree with your proposed solution on this one.

> d) remove problems trying to associate related commit IDs e.g.  when 
>    someone changes email address frequently and solve that problem once 
>    and for all.

People will usually retain the same Real Name part of the ID, so we can 
match quite well using that when the email address changes.

> For a) I guess the best we can do is add some checking for insane commit
> and author IDs like containing "localhost", not setting a name or
> containing an IP address. I'd also like to add something to the commit
> policy about only committing using sane IDs, commits with invalid IDs
> are at risk of being reverted.

I'm very happy with that solution, and fully agree that the policy must 
mandate sane IDs and we must forcefully reject with extreme prejudice 
any commits without a valid ID.

> How does that sound?

I'm very happy with your proposal.  Thanks for taking my views into account.

-- Rod