[Mesa-dev] GitLab migration update

[Rob Clark]

On Thu, Jun 7, 2018 at 3:25 AM, Daniel Stone <daniel at fooishbar.org> wrote:
> Hi,
>
> On 2 June 2018 at 16:45, Jason Ekstrand <jason at jlekstrand.net> wrote:
>> When the migration happens, there will be a very brief (less than 30
>> minutes?) period during which no one will be able to push to either repo.
>> I'll fire off an e-mail as well as messages in #dri-devel and #intel-3d
>> shortly before we actually take the repo offline so that everyone has a bit
>> of warning.  Once the transition is complete, you'll have to change the git
>> remote you use for pushing to point to gitlab.  That should be the ONLY
>> change to your current workflow and otherwise things should continue to work
>> smoothly.  If someone accidentally tries to push to the remote on
>> git.freedesktop.org, the push will fail and they will receive a message
>> reminding them to push to gitlab instead.
>>
>> When the mesa repo gets imported into gitlab, I will be disabling all of the
>> "fancy" features such as merge requests, wikis, issue tracking, etc.  They
>> are there for us to use if we want, but the first change to make is simply
>> going to be a repo hosting change.
>
> All of the above has been done, and the following repos now have their
> primary (and only push) source under
> https://gitlab.freedesktop.org/mesa/:
>   crucible demos drm glu glut kmscube mesa piglit shader-db vkpipeline-db
>
> The following empty/junk repos were removed:
>   llvm mesa-test piglit-test
>
> The following dormant repos were _not_ migrated, but can be migrated
> (perhaps to an archive/ section?) if they are still useful:
>   clover glw libwsbm linux-agp-compat r600_demo rbug-gui
>

so, I do actually use rbug-gui about once every three years (ofc by
then it is totally out of date after three years of gallium api
changes since I last used it.. I don't really remember why it doesn't
live in the mesa git tree)

BR,
-R

> The following repo I don't really know what to do with, but will chase
> up with Jason:
>   tasks
>
> The following repo I'll separately chase up with VMware people about:
>   vmwgfx
>
> Please ping me if you have any problems.
>
> Cheers,
> Daniel