[gdal-dev] Trac to GitHub

Mateusz Loskot mateusz at loskot.net
Mon Mar 19 10:32:22 PDT 2018


On 19 March 2018 at 18:14, Even Rouault <even.rouault at spatialys.com> wrote:
>>> 3) Close all Trac tickets with assignment to a "closed-before-github-
>>> migration" milestone, and a message "Issue reporting has now been migrated >to
>> https://github.com/OSGeo/gdal/issues..."
>>
>>I guess, you mean manual action
>
> Manual action, but lukily to be done just once for all tickets (batch action)
>
> Basically open
> https://trac.osgeo.org/gdal/query?status=assigned&status=new&status=reopened&max=1000
>
> and if you have the sufficient rights, click on the top-left checkbox to select all the tickets,
> go to the bottom to the "Batch modify" tab, and define a milestone, add a comment and click on "Change tickets"
> So a 1-minute action.

THAT, I can do ;)


>> > git filter-branch -f --msg-filter 'python /home/even/rewrite.py'  -- trunk
>> > [...]
>>
>> You lost me shortly after the while True, I suck at advanced git terribly :)
>
> Huh that's just my-not-so-idiomatic Python hacking to parse the old commit message and change it ;-)

Actually, it was `git filter-branch` that already sent me off :)


>> The main goal is to apply semantic to the raw numbers, even fi the URL>> gets broken
>> in future (eg. read-only GDAL Trac moves to some archives server).
>
> Yes the point is to make it obvious that those are references to Trac and not github issues.
>
> I'm preparing a RFC to summarize various aspects and have some official plan that can be discussed.

Thank you!

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net


More information about the gdal-dev mailing list