Re: Verifying the git repo

[Christian Grobmeier <gr...@gmail.com>]

I looked at it and could not find any issue (except duplicate tags)
Lets go for it!

Cheers


On Fri, Nov 30, 2012 at 4:38 PM, Ivan Habunek <iv...@gmail.com> wrote:
> Heads up,
>
> If no problems are found by Monday (T+3) then I will notify infra to
> continue with the migration process.
>
> Please take a little time to review the repo and reply to the list if
> you have any objections or remarks.
>
> Regards,
> Ivan
>
> On 30 November 2012 08:09, Ivan Habunek <iv...@gmail.com> wrote:
>> Hi all,
>>
>> The new git repository is set up and located at:
>> https://git-wip-us.apache.org/repos/asf/logging-log4php.git
>>
>> Quoting:
>> "It is the responsibility of each project to review the Git history in
>> their new repository before it is made the official repository. In the
>> event that a project has to revert to SVN due to a bad Git clone, it
>> is the project's responsibility to reapply writes made to Git back to
>> SVN. It is in the project's best interest to make sure that the
>> history is correct before starting to use it as an official
>> repository."
>> -- from https://git-wip-us.apache.org/docs/switching-to-git.html
>>
>> I will try to verify everything is good, but I would appreciate extra
>> sets of eyes on this one! So clone and compare with svn if you have
>> the time, and report any issues here. Thanks!
>>
>> There is one known issue, since we renamed our tags to be compatible
>> with Composer, they seem to appear twice for each released version.
>> E.g. both old style: "apache-log4php-2.3.0" and new: "2.3.0". This
>> should not present a problem, we'll just delete the old tag style
>> after migration is final.
>>
>> Regards,
>> Ivan



-- 
http://www.grobmeier.de
https://www.timeandbill.de

Re: Verifying the git repo

[Ivan Habunek <iv...@gmail.com>]

Since nobody had any objections, I asked Gavin to go ahead with the
migration procedure.

May FSM grant us luck. :-)

Regards,
Ivan

On 3 December 2012 10:23, Christian Grobmeier <gr...@gmail.com> wrote:
> I looked at it and could not find any issue (except duplicate tags)
> Lets go for it!
>
> Cheers
>
>
> On Fri, Nov 30, 2012 at 4:38 PM, Ivan Habunek <iv...@gmail.com> wrote:
>> Heads up,
>>
>> If no problems are found by Monday (T+3) then I will notify infra to
>> continue with the migration process.
>>
>> Please take a little time to review the repo and reply to the list if
>> you have any objections or remarks.
>>
>> Regards,
>> Ivan
>>
>> On 30 November 2012 08:09, Ivan Habunek <iv...@gmail.com> wrote:
>>> Hi all,
>>>
>>> The new git repository is set up and located at:
>>> https://git-wip-us.apache.org/repos/asf/logging-log4php.git
>>>
>>> Quoting:
>>> "It is the responsibility of each project to review the Git history in
>>> their new repository before it is made the official repository. In the
>>> event that a project has to revert to SVN due to a bad Git clone, it
>>> is the project's responsibility to reapply writes made to Git back to
>>> SVN. It is in the project's best interest to make sure that the
>>> history is correct before starting to use it as an official
>>> repository."
>>> -- from https://git-wip-us.apache.org/docs/switching-to-git.html
>>>
>>> I will try to verify everything is good, but I would appreciate extra
>>> sets of eyes on this one! So clone and compare with svn if you have
>>> the time, and report any issues here. Thanks!
>>>
>>> There is one known issue, since we renamed our tags to be compatible
>>> with Composer, they seem to appear twice for each released version.
>>> E.g. both old style: "apache-log4php-2.3.0" and new: "2.3.0". This
>>> should not present a problem, we'll just delete the old tag style
>>> after migration is final.
>>>
>>> Regards,
>>> Ivan
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de