Git Migration: Status Update for Todays Migration

13 years ago by David Soria Parra — view source

unread

Hi Internals,

we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.

Thanks do Alexander Moskaliov we now have a much better, rewritten Mail script.
Thanks to Florian Anderiasch we have a bugweb script.

I added a wiki page for the workflow at http://wiki.php.net/vcs/gitworkflow.
So far nobody has added questions to the gitfaq or the asked questions
about the workflow (except for stas). Please let me know what you need
to know to be able to work with git and I will try to clarify it as
much as possible. Also, I would encourage people to contribute to
the gitfaq and the gitworkflow page.

Questions?
David

13 years ago by Stefan Marr — view source

unread

Hi David:

Hi Internals,

we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.

Thanks do Alexander Moskaliov we now have a much better, rewritten Mail script.
Thanks to Florian Anderiasch we have a bugweb script.
Thanks!

I added a wiki page for the workflow at http://wiki.php.net/vcs/gitworkflow.
So far nobody has added questions to the gitfaq or the asked questions
about the workflow (except for stas).

The workflow has one practical drawback over the current sparse checkout one.
For me, switching branches also implies redoing configure and make, doesn't it?
That adds quite a bit of overhead to build and test times.

Thus, I would suggest to document the workflow with different folders for the major branches.

Or, in case there is a better way, please let me know.

Thanks
Stefan

--
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax: +32 2 629 3525

13 years ago by Marco Pivetta — view source

unread

@Stefan: travis could be setup to build PHP and check your branches on your
own fork whenever you push... That would reduce some of the overhead
hopefully.

Marco Pivetta

http://twitter.com/Ocramius

http://marco-pivetta.com

Hi David:

Hi Internals,

we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.

Thanks do Alexander Moskaliov we now have a much better, rewritten Mail
script.
Thanks to Florian Anderiasch we have a bugweb script.
Thanks!

I added a wiki page for the workflow at
http://wiki.php.net/vcs/gitworkflow.
So far nobody has added questions to the gitfaq or the asked questions
about the workflow (except for stas).

The workflow has one practical drawback over the current sparse checkout
one.
For me, switching branches also implies redoing configure and make,
doesn't it?
That adds quite a bit of overhead to build and test times.

Thus, I would suggest to document the workflow with different folders for
the major branches.

Or, in case there is a better way, please let me know.

Thanks
Stefan

--
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax: +32 2 629 3525

13 years ago by David Soria Parra — view source

unread

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David:

Hi Internals,

we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.

Thanks do Alexander Moskaliov we now have a much better,
rewritten Mail script. Thanks to Florian Anderiasch we have a
bugweb script.
Thanks!

I added a wiki page for the workflow at
http://wiki.php.net/vcs/gitworkflow. So far nobody has added
questions to the gitfaq or the asked questions about the workflow
(except for stas).

The workflow has one practical drawback over the current sparse
checkout one. For me, switching branches also implies redoing
configure and make, doesn't it? That adds quite a bit of overhead
to build and test times.
Yes.

You can hover just clone locally (git will use hardlinks) and checkout
different branches.

Thus, I would suggest to document the workflow with different
folders for the major branches.
That would break all the merging mechanics and the branch semantics.

Or, in case there is a better way, please let me know.

Thanks Stefan

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPZi3XAAoJEAT0aMuPE7Z1te4P/2Spbr4hKxnKa6IOuW62IRYC
BqAxrxe+VsN7QBRAWF4eMan8cJjqfnHeX3BSc0gPiVfgZmZNdtrvvKEMK0yS5qmt
KAyTRmA5BoxuZYHHBQ/29aM3fkaiv9q6GfJ7fto+8UMtuhgHgf0wHZtQgix/3Z5l
I74Kc24JlryiRHerSLjRhxQu9fUoprb8ybsVTfrQaIbijag51l3qEN0kOX7yRKln
c1FHNoLNeCn+M1k1TVn+2ocIBhAN2vlcCtgipgVzZLeD1rByjQVam+ChsU0z9jLt
fX36rEZqQ3Oxbi6K/+qE2HvaQEZz3T2T0YExKlnD9ayQBXFqx7MRsvedm1jw/W20
IgQwWmIgFaCMX4I2uRscTvkOE1CrIsgFMgiX+lvJijeUgd8rYFT0h2BiWlbzoQYr
ME7wGcFOMGep7/caSgMV5ckgSW00LEuQ8hxbshrK2R1afpTm0pivhcHwGwAQZ4iD
RU9E8eOVbyJuGwTOEe9ou6X2IDG7kP0IUkV1js5StUq4szlyXYV6YvTRfrupx+H8
nRwSLO009Fv2Idp6WFWRb5iLqalXCjkNWJ3mrCMJiMRzrZ72w8v1Iz4Jr36aQvTW
YuZce3wCTYdAeFwlZZPp1zavgZv1j+B9AOh3nSqLN6hzGjUuzhEQhAfPt+VfZf8W
kDOs3hqcgxytV8mcT5GY
=x4YU
-----END PGP SIGNATURE

13 years ago by Derick Rethans — view source

unread

David Soria Parra dsp@php.net wrote:

we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.
You'll leave it going read-only for a while I hope? I assume quite a few people have uncommitted patches.

cheers,
Derick

13 years ago by David Soria Parra — view source

unread

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Soria Parra dsp@php.net wrote:

we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.
You'll leave it going read-only for a while I hope? I assume quite
a few people have uncommitted patches.
Absolutly. There is no plan to shutdown the server itself. Everything
will be read only for at least this year.

cheers, Derick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPZi3+AAoJEAT0aMuPE7Z1WvkQALcaops48lLd+cJ3QYE8hs8n
g0dlTxwX2smtBidi1X3IRPUMKX87hDZardM14OYY9CqqYokv+HbI5VsQoSeh4RsM
41Nn2cyYmsYLl1b+rCbDE6iL2CejtSxFbgUW5aYfWuUyyydocmGy1qxE/0aniSUN
5p+/hfpx36ZTF//adZHPNKpICkKFCW5pVzUfmi0MugllVRWUgqqfVlot/fOjg2Gp
4sJZqzj8s1c0V0cYnIFoSDrwr6NMzf2XqGHFodrYjnOuYjED3JokqC3Kr4Z8I1nA
Yp+iVc7ZCIaZqaRuOC3hz2kzbLrTr4S6ZxUDG7bv/G0zxiVeL3JHie0wUK1hV63q
MZ1aLaCnPVsmmTlwRs8pbVqmEMdSMjYZhZNeiU8oqK1ZpR0HqssvAZpJX9sw6P/E
p0MhMWUFohTwy7xQZ+RYN702XFYuwzDh4gaElQXo8q0iN6eExwkjdxW1t2y7ZXmM
QIhJ2Ws1E9GWEex9EopgXVn5LjUHx1pFU/6MFwbW43yGngmX34ycvaK4WKO01l6b
ldRjOLYaTrxhWi78Zbs8QgZgRycOBu7yFzIFcR1d1MwEZFW1tGzaBNjAO6yi/+FL
Zhaql8SVQXzw8SOmgGDAEN7s1TcU463NOvETdDx33+/mRwnoSGcq9aL7cMPVvXGU
4gCX+faMq5DZNC10xNaw
=eF+M
-----END PGP SIGNATURE