[gentoo-dev] eselect git repo

[gentoo-dev] eselect git repo

[Ulrich Mueller]

Hi all,

Just a heads up, lu_zero has discovered that the eselect git
repository contains some commits with invalid author lines. This is a
holdover from the conversion from svn to git (basically, the real name
is missing for devs who changed their Gentoo username). I'm going to
fix this within the next few days, but I believe this means that the
history will change.

So, please don't push to the eselect repo until I give the all-clear.

Ulrich

[gentoo-dev] Re: eselect git repo

[Ulrich Mueller]

>>>>> On Thu, 26 Apr 2012, I wrote:

> Just a heads up, lu_zero has discovered that the eselect git
> repository contains some commits with invalid author lines. This is
> a holdover from the conversion from svn to git (basically, the real
> name is missing for devs who changed their Gentoo username). I'm
> going to fix this within the next few days, but I believe this means
> that the history will change.

> So, please don't push to the eselect repo until I give the
> all-clear.

To the best of my knowledge, the repo should be fixed now. Please note
that the history has changed. So either do a fresh git clone or follow
git-rebase(1), section "RECOVERING FROM UPSTREAM REBASE".

(And apologies for the spam in #gentoo-commits. I hadn't expected that
all these commits would be reported to cia.vc, otherwise I'd have
asked infra to temporarily disable it in the commit hook.)

Ulrich

Re: [gentoo-dev] Re: eselect git repo

[Luca Barbato]

On 28/04/12 08:44, Ulrich Mueller wrote:
>>>>>> On Thu, 26 Apr 2012, I wrote:
> 
>> Just a heads up, lu_zero has discovered that the eselect git
>> repository contains some commits with invalid author lines. This is
>> a holdover from the conversion from svn to git (basically, the real
>> name is missing for devs who changed their Gentoo username). I'm
>> going to fix this within the next few days, but I believe this means
>> that the history will change.
> 
>> So, please don't push to the eselect repo until I give the
>> all-clear.
> 
> To the best of my knowledge, the repo should be fixed now. Please note
> that the history has changed. So either do a fresh git clone or follow
> git-rebase(1), section "RECOVERING FROM UPSTREAM REBASE".
> 

Thank you a lot =)

lu

-- 

Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero