* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-09 21:45 ` hasufell
@ 2014-06-09 22:12 ` Tom Wijsman
2014-06-10 8:57 ` Thomas Kahle
` (2 subsequent siblings)
3 siblings, 0 replies; 56+ messages in thread
From: Tom Wijsman @ 2014-06-09 22:12 UTC (permalink / raw
To: gentoo-dev; +Cc: hasufell
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
On Mon, 09 Jun 2014 21:45:26 +0000
hasufell <hasufell@gentoo.org> wrote:
> Probably because no one mentored them on how to fix these QA issues.
> Otherwise... if that's attitude, then that's just sad and has to be
> fixed by those who run that overlay (review, contribution guidelines).
>
> And I still think that the top 1 reason people run an overlay is
> because it's easier than contributing directly.
> A lot of overlay maintainers I tried to convince on getting more
> involved even said that.
>
> Even sunrise workflow has proven too slow and cumbersome... look at
> the commit history, it's constantly decreasing.
>
> Sure, reasons may vary, but there is not much positive to say about
> current gentoo workflow.
We are setting up https://github.com/gentoo/proxy-maintainers to deal
with some of these problems; if sunrise continues to decrease activity,
I suspect this repository has a chance to become its successor.
Travis integration is used to cover QA issues, see
https://travis-ci.org/gentoo/proxy-maintainers which runs repoman on
the overlay for each commit; therefore, QA issues don't go unnoticed.
To improve the workflow further; we use app-portage/overlint to catch
differences between that repository and the Portage tree, after which
there is room for even much more automation; thus more time reviewing.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-09 21:45 ` hasufell
2014-06-09 22:12 ` Tom Wijsman
@ 2014-06-10 8:57 ` Thomas Kahle
2014-06-10 11:44 ` Rich Freeman
2014-06-10 12:09 ` Tom Wijsman
2014-06-10 10:30 ` Christopher Schwan
2014-06-10 15:45 ` Andrew Savchenko
3 siblings, 2 replies; 56+ messages in thread
From: Thomas Kahle @ 2014-06-10 8:57 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]
On 09.06.2014 23:45, hasufell wrote:
> Thomas Kahle:
>> then they stay in the overlay
>> because people feel it is not worth the effort to fix the QA
>> issues which in turn would be necessary before moving them to the
>> main tree.
>>
>
> Probably because no one mentored them on how to fix these QA issues.
> Otherwise... if that's attitude, then that's just sad and has to be
> fixed by those who run that overlay (review, contribution guidelines).
I was mentored on the QA issues and have come to 'this attitude'
myself. Take sci-mathematics/singular: Upstream is genuinely not
interested in supporting distriutions or their petty QA unless
you can prove them that there is a problem that massively hurts
them. Fixing compatibility with user specified LDFLAGS? They'll
laugh at you. Their attitude is a result of years and years of
struggling with too little manpower themselves. They can hardly
keep up with scientific developments.
My personal attitude: It is just not worth the effort to rewrite
their build systems for the ~10 users out there. I have better
things to do with my time and I think that these packages can
live forever in the overlay and that is completely OK this way.
> And I still think that the top 1 reason people run an overlay is because
> it's easier than contributing directly.
> A lot of overlay maintainers I tried to convince on getting more
> involved even said that.
I think that's a different point. I've also met people who just
don't want to become developers because their "it's not worth my
time" boundary is on the other side of the quizzes. So one could
say yes, contributing to overlays is convenient enough to never
do quizzes. The arguments I have heard are not about bugzilla
workflow. They are: I don't get that much more from being a full
dev, so I don't bother taking the quizzes.
> Even sunrise workflow has proven too slow and cumbersome... look at the
> commit history, it's constantly decreasing.
I don't know sunrise.
> Sure, reasons may vary, but there is not much positive to say about
> current gentoo workflow.
Here's a positive thing: There are many ways to contribute, even
without taking lenghty quizzes :)
Cheers,
Thoams
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 8:57 ` Thomas Kahle
@ 2014-06-10 11:44 ` Rich Freeman
2014-06-10 17:11 ` Peter Stuge
2014-06-10 12:09 ` Tom Wijsman
1 sibling, 1 reply; 56+ messages in thread
From: Rich Freeman @ 2014-06-10 11:44 UTC (permalink / raw
To: gentoo-dev
On Tue, Jun 10, 2014 at 4:57 AM, Thomas Kahle <tomka@gentoo.org> wrote:
>
> My personal attitude: It is just not worth the effort to rewrite
> their build systems for the ~10 users out there. I have better
> things to do with my time and I think that these packages can
> live forever in the overlay and that is completely OK this way.
I think this is a fairly common issue, actually. Many ebuilds live
out in overlays (if they're lucky) or just in bugzilla (if not) simply
because they have QA issues that nobody wants to deal with. I've seen
ebuilds in bugzilla that get bumped as regularly as anything in the
tree.
QA can be a double-edged sword. Sometimes it can turn a good ebuild
into a great one. At other times it can result in a fair-to-good
ebuild leaving the tree entirely.
I don't see overlays as a problem though. The main issue I've seen
with them is when people make changes to the tree that requires
updating reverse dependencies they don't update overlays, and users
using overlays can end up being in a broken state for a time.
Obviously we can never control whether overlays get updated, but we
could require tree-wide updates like this to get announced, instead of
just having a tracking bug that only notifies maintainers of impacted
packages/etc. That would be more noise though, and likely
bikeshedding that those making the changes want to avoid. Or we can
just accept that those using overlays will have them break from time
to time.
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 11:44 ` Rich Freeman
@ 2014-06-10 17:11 ` Peter Stuge
0 siblings, 0 replies; 56+ messages in thread
From: Peter Stuge @ 2014-06-10 17:11 UTC (permalink / raw
To: gentoo-dev
Rich Freeman wrote:
> likely bikeshedding
..
> Or we can just accept that those using overlays will have them
> break from time to time.
Maybe there's an in-between. It's very reasonable to ask from an
overlay maintainer that they run overlint now and then. If overlint
can be taught to report whenever something breaks, I think that might
be good enough.
Anyone not bothering to run overlint (like me) knows what they are
getting themselves into.
//Peter
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 8:57 ` Thomas Kahle
2014-06-10 11:44 ` Rich Freeman
@ 2014-06-10 12:09 ` Tom Wijsman
1 sibling, 0 replies; 56+ messages in thread
From: Tom Wijsman @ 2014-06-10 12:09 UTC (permalink / raw
To: gentoo-dev; +Cc: tomka
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
On Tue, 10 Jun 2014 10:57:32 +0200
Thomas Kahle <tomka@gentoo.org> wrote:
> I was mentored on the QA issues and have come to 'this attitude'
> myself. Take sci-mathematics/singular: Upstream is genuinely not
> interested in supporting distriutions or their petty QA unless
> you can prove them that there is a problem that massively hurts
> them. Fixing compatibility with user specified LDFLAGS? They'll
> laugh at you. Their attitude is a result of years and years of
> struggling with too little manpower themselves. They can hardly
> keep up with scientific developments.
>
> My personal attitude: It is just not worth the effort to rewrite
> their build systems for the ~10 users out there. I have better
> things to do with my time and I think that these packages can
> live forever in the overlay and that is completely OK this way.
Yeah, it behaves like a trade-off in manpower; the type of QA brought
up here is an enhancement, where it would be nice if someone could make
the *FLAGS, CC, LD, ... supported but definitely not a requirement.
This is not a reason to keep it in an overlay (or block stabilization).
> I think that's a different point. I've also met people who just
> don't want to become developers because their "it's not worth my
> time" boundary is on the other side of the quizzes. So one could
> say yes, contributing to overlays is convenient enough to never
> do quizzes. The arguments I have heard are not about bugzilla
> workflow. They are: I don't get that much more from being a full
> dev, so I don't bother taking the quizzes.
Yes; becoming a full Gentoo Developer can help to go across certain
restrictions, as well as can become more handy if you do work all over
the place in the Portage tree. Other than that I think there is a lot
you can get accomplished as an user; that is, if there is enough
manpower to make those accomplishments of the users have an effect:
https://wiki.gentoo.org/wiki/Project:Gentoo/Staffing_Needs
> Here's a positive thing: There are many ways to contribute, even
> without taking lenghty quizzes :)
Indeed, here is a lengthy summary that is probably not complete:
https://wiki.gentoo.org/wiki/Contributing_to_Gentoo
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-09 21:45 ` hasufell
2014-06-09 22:12 ` Tom Wijsman
2014-06-10 8:57 ` Thomas Kahle
@ 2014-06-10 10:30 ` Christopher Schwan
2014-06-10 10:42 ` Alexander Berntsen
2014-06-10 15:45 ` Andrew Savchenko
3 siblings, 1 reply; 56+ messages in thread
From: Christopher Schwan @ 2014-06-10 10:30 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 2818 bytes --]
On Monday 09 June 2014 21:45:26 hasufell wrote:
> Probably because no one mentored them on how to fix these QA issues.
> Otherwise... if that's attitude, then that's just sad and has to be
> fixed by those who run that overlay (review, contribution guidelines).
>
> And I still think that the top 1 reason people run an overlay is because
> it's easier than contributing directly.
> A lot of overlay maintainers I tried to convince on getting more
> involved even said that.
>
> Even sunrise workflow has proven too slow and cumbersome... look at the
> commit history, it's constantly decreasing.
>
> Sure, reasons may vary, but there is not much positive to say about
> current gentoo workflow.
Since I was mentioned here - I am one of sage overlay[1] developers - it is
maybe worth sharing my point of view as someone that is not a Gentoo
developer. The recent discussion[2] with hasufell on our overlay might also be
interesting.
I have to agree that indeed it is easier to contribute to an overlay, in my
case because of
a) git and
b) github.
As far as I am up-to-date the main Gentoo repository is still managed by cvs,
right? Thats something I really would not like to work with. Not because cvs
is inferior to git (I hope no one feels offended) but because now I am so used
to and pleased with the workflow that comes with git that I can not even think
of changing that.
What I really love about github (and I don't think that similar platform
differ much here) is the fact that it allows me to comment on /everything/. I
can comment on commits that maybe lack something, which could then result in a
new Issue; a user could be faster than I and create a pull request that fixes
this problem. Maybe there is another mistake which I tell him there so he
adjusts his commit and I finally accept it. Sometimes, after some months I
wonder why we decided about some things the way we did and I can look it up in
the Issue. There is the _complete_ discussion with direct references to the
code and all people involved.
If there is a lession that I learned here, than that centralizing
communications and development in one place was beneficial for us. Whether
this also applies to the Gentoo project - well, I don't know. Right now there
are several mailing lists, IRC channels and the Bugzilla so in comparison to
our little overlay it is quite decentralized. Adding another way, e.g. via
github, could complicate the situation but it will defintely get the project
more user contributions (if that is needed).
In any case, I believe that the migration to git would be a huge step forward
and it would attract at least one pontential new developer ;). Any update on
this?
[1] https://github.com/cschwan/sage-on-gentoo
[2] https://github.com/cschwan/sage-on-gentoo/issues/294
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 10:30 ` Christopher Schwan
@ 2014-06-10 10:42 ` Alexander Berntsen
0 siblings, 0 replies; 56+ messages in thread
From: Alexander Berntsen @ 2014-06-10 10:42 UTC (permalink / raw
To: gentoo-dev
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
For what it's worth, I strongly oppose using GitHub or any other SaaSS
that is not licensed using AGPL or under similar terms.
My suggestion is Phabricator, which additionally beats GitHub on
functionality by having proper code review support. I will however not
oppose any momentum for a different self-hosted free software solution.
- --
Alexander
bernalex@gentoo.org
https://secure.plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlOW4PgACgkQRtClrXBQc7U7JQD+Lg9mKq+Y/pW9bSUDAxLkTxSP
9D2E18qGh9Ce/ZBQAXMA/RiqRN9QGtqIPGBVah3ZOXa8zV4FBP0CVqSZhNECZ6JB
=mTUU
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-09 21:45 ` hasufell
` (2 preceding siblings ...)
2014-06-10 10:30 ` Christopher Schwan
@ 2014-06-10 15:45 ` Andrew Savchenko
2014-06-10 15:49 ` Alexander Berntsen
2014-06-10 22:59 ` [gentoo-dev] The infinite git migration Patrick Lauer
3 siblings, 2 replies; 56+ messages in thread
From: Andrew Savchenko @ 2014-06-10 15:45 UTC (permalink / raw
To: gentoo-dev; +Cc: hasufell
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Hello,
On Mon, 09 Jun 2014 21:45:26 +0000 hasufell wrote:
> Thomas Kahle:
> > then they stay in the overlay
> > because people feel it is not worth the effort to fix the QA
> > issues which in turn would be necessary before moving them to the
> > main tree.
> >
>
> Probably because no one mentored them on how to fix these QA issues.
> Otherwise... if that's attitude, then that's just sad and has to be
> fixed by those who run that overlay (review, contribution guidelines).
>
> And I still think that the top 1 reason people run an overlay is because
> it's easier than contributing directly.
> A lot of overlay maintainers I tried to convince on getting more
> involved even said that.
As for my own overlay, most of packages there are just either
bugfixes already in bugzilla and pending there (often for years) or
extra packages nobody cares to add despite bugs. I don't want to
blame anyone, project is understuffed and people are overburdened.
But even for those became Gentoo devs it is not so easy to fix
other people's packages due to quite strict and complicated rules
about touching other people's stuff.
So the problem is not in overlays being easier, but in overlays
being often the only way to have required or fixed packages.
Another issue is that CVS is outdated if not retarded compared to
Git. CVS was great 15 years ago, but today Git is far more
productive for distributed collaborative development. Probably the
most terrible issues are how CVS manages directories, renames; and
branches support is really weird.
I don't know why CVS is still used for Gentoo main repository,
probably some infrastructure elements depends deeply on its
internals, because I see of no other reason why Git is still not
used despite efforts ongoing for last several years.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 15:45 ` Andrew Savchenko
@ 2014-06-10 15:49 ` Alexander Berntsen
2014-06-10 16:45 ` Andrew Savchenko
2014-06-10 22:59 ` [gentoo-dev] The infinite git migration Patrick Lauer
1 sibling, 1 reply; 56+ messages in thread
From: Alexander Berntsen @ 2014-06-10 15:49 UTC (permalink / raw
To: gentoo-dev
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/06/14 17:45, Andrew Savchenko wrote:
> I don't know why CVS is still used for Gentoo main repository,
> probably some infrastructure elements depends deeply on its
> internals, because I see of no other reason why Git is still not
> used despite efforts ongoing for last several years.
Infra can probably speak for themselves, but Portage with its history
is crazy big, and git is not great with crazy big projects. What you
commonly do in those situations is obviously make it more modular and
have several repositories. My guess is this process of figuring out
how to git efficiently isn't progressing too rapidly.
- --
Alexander
bernalex@gentoo.org
https://secure.plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlOXKPsACgkQRtClrXBQc7Vp5wD+Ib697vg0VF2WRi//CZfaQ1Id
cWMnkGSio22Vxv4NhdcBAIvGImYta4Ajkg/CXsHHPTBVsZNAMtPXubMYSec2ExQB
=g9ID
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 15:49 ` Alexander Berntsen
@ 2014-06-10 16:45 ` Andrew Savchenko
2014-06-10 17:09 ` Rich Freeman
` (2 more replies)
0 siblings, 3 replies; 56+ messages in thread
From: Andrew Savchenko @ 2014-06-10 16:45 UTC (permalink / raw
To: gentoo-dev; +Cc: Alexander Berntsen
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
On Tue, 10 Jun 2014 17:49:15 +0200 Alexander Berntsen wrote:
> On 10/06/14 17:45, Andrew Savchenko wrote:
> > I don't know why CVS is still used for Gentoo main repository,
> > probably some infrastructure elements depends deeply on its
> > internals, because I see of no other reason why Git is still not
> > used despite efforts ongoing for last several years.
> Infra can probably speak for themselves, but Portage with its history
> is crazy big, and git is not great with crazy big projects.
Why are you saying that git is inefficient with large projects? It
was developed with efficiency in mind in the first place. And
kernel guys will likely disagree with "git is not great with crazy
big projects" statement. And with git kernel bisection and other
complicated (in terms or data manipulation) operations are quite
fast even on old hardware.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 16:45 ` Andrew Savchenko
@ 2014-06-10 17:09 ` Rich Freeman
2014-06-11 4:10 ` [gentoo-dev] " Ryan Hill
2014-06-10 19:58 ` [gentoo-dev] " hasufell
2014-06-11 12:59 ` Alexander Berntsen
2 siblings, 1 reply; 56+ messages in thread
From: Rich Freeman @ 2014-06-10 17:09 UTC (permalink / raw
To: gentoo-dev; +Cc: Alexander Berntsen
On Tue, Jun 10, 2014 at 12:45 PM, Andrew Savchenko <bircoph@gmail.com> wrote:
>
> Why are you saying that git is inefficient with large projects? It
> was developed with efficiency in mind in the first place. And
> kernel guys will likely disagree with "git is not great with crazy
> big projects" statement.
The kernel tree that "everybody" uses has only a single committer -
Linus. That is definitely a potential challenge that we may run into
migrating gentoo-x86 - we have many committers and a fairly high
commit rate.
With Linux you have a million separate git repos and everybody
cascades their changes up, which get merged into bigger and bigger
patch sets. So, Linus might get a set of updates to merge from the
video driver maintainer and it might contain 400 bundled commits, but
it isn't like the 400 committers have direct access to Linus's tree.
They all commit to their own trees and cascade up to the next level
via email.
We already have a working method of migrating the entire portage
history to git. However, the infra tools/etc are all built around git
and only a few people have access to update them. The git repository
needs to make it out to the mirrors/etc.
There are also a bunch of process-related details to work out. Does
everybody try to rebase onto master, or do we have lots of merges?
What happens if you do rebase onto master and then when you go to push
it isn't a fast-forward any longer because somebody else pushed first?
But, for the most part we just need to get the back-end re-written to
work with a git repo. Actually migrating the tree itself to git is
largely a solved problem.
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread
* [gentoo-dev] Re: The state and future of the OpenRC project
2014-06-10 17:09 ` Rich Freeman
@ 2014-06-11 4:10 ` Ryan Hill
2014-06-11 4:17 ` Patrick Lauer
2014-06-11 4:18 ` Duncan
0 siblings, 2 replies; 56+ messages in thread
From: Ryan Hill @ 2014-06-11 4:10 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
On Tue, 10 Jun 2014 13:09:26 -0400
Rich Freeman <rich0@gentoo.org> wrote:
> On Tue, Jun 10, 2014 at 12:45 PM, Andrew Savchenko <bircoph@gmail.com> wrote:
> >
> > Why are you saying that git is inefficient with large projects? It
> > was developed with efficiency in mind in the first place. And
> > kernel guys will likely disagree with "git is not great with crazy
> > big projects" statement.
>
> The kernel tree that "everybody" uses has only a single committer -
> Linus. That is definitely a potential challenge that we may run into
> migrating gentoo-x86 - we have many committers and a fairly high
> commit rate.
>
> With Linux you have a million separate git repos and everybody
> cascades their changes up, which get merged into bigger and bigger
> patch sets. So, Linus might get a set of updates to merge from the
> video driver maintainer and it might contain 400 bundled commits, but
> it isn't like the 400 committers have direct access to Linus's tree.
> They all commit to their own trees and cascade up to the next level
> via email.
>
> We already have a working method of migrating the entire portage
> history to git. However, the infra tools/etc are all built around git
> and only a few people have access to update them. The git repository
> needs to make it out to the mirrors/etc.
>
> There are also a bunch of process-related details to work out. Does
> everybody try to rebase onto master, or do we have lots of merges?
> What happens if you do rebase onto master and then when you go to push
> it isn't a fast-forward any longer because somebody else pushed first?
>
> But, for the most part we just need to get the back-end re-written to
> work with a git repo. Actually migrating the tree itself to git is
> largely a solved problem.
Weren't we also waiting for some gpg signing stuff to land?
--
Ryan Hill psn: dirtyepic_sk
gcc-porting/toolchain/wxwidgets @ gentoo.org
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 475 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] Re: The state and future of the OpenRC project
2014-06-11 4:10 ` [gentoo-dev] " Ryan Hill
@ 2014-06-11 4:17 ` Patrick Lauer
2014-06-11 11:38 ` Rich Freeman
2014-06-11 4:18 ` Duncan
1 sibling, 1 reply; 56+ messages in thread
From: Patrick Lauer @ 2014-06-11 4:17 UTC (permalink / raw
To: gentoo-dev
On 06/11/2014 12:10 PM, Ryan Hill wrote:
>> But, for the most part we just need to get the back-end re-written to
>> work with a git repo. Actually migrating the tree itself to git is
>> largely a solved problem.
>
> Weren't we also waiting for some gpg signing stuff to land?
>
That's completely orthogonal (but would be convenient to have as a
built-in, which git since ~1.8 does)
Since people can't even decide on a key policy in under 5 years I doubt
signing is important enough ...
Now git has some/all of the needed features, and people wait on a future
potential git migration instead of figuring out the important bits now
(a good part of that is defined in GLEP 63, but there's no action apart
from work on gentoo-keys.I don't have motivation to try pusing this
again this year ...)
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] Re: The state and future of the OpenRC project
2014-06-11 4:17 ` Patrick Lauer
@ 2014-06-11 11:38 ` Rich Freeman
0 siblings, 0 replies; 56+ messages in thread
From: Rich Freeman @ 2014-06-11 11:38 UTC (permalink / raw
To: gentoo-dev
On Wed, Jun 11, 2014 at 12:17 AM, Patrick Lauer <patrick@gentoo.org> wrote:
> Now git has some/all of the needed features, and people wait on a future
> potential git migration instead of figuring out the important bits now
> (a good part of that is defined in GLEP 63, but there's no action apart
> from work on gentoo-keys.I don't have motivation to try pusing this
> again this year ...)
Well, the folks doing the git migration are basically waiting for the
infra pieces to be done.
A challenge here is that nobody has time, and sometimes the argument
gets made that there is no sense doing A because you can't use it
without B. The reality is that we need A, B, C, D, E to cut over, and
none of them are useful on their own, so if everybody makes this
argument we take no action.
The actual migration and git tools should be fine now.
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread
* [gentoo-dev] Re: The state and future of the OpenRC project
2014-06-11 4:10 ` [gentoo-dev] " Ryan Hill
2014-06-11 4:17 ` Patrick Lauer
@ 2014-06-11 4:18 ` Duncan
1 sibling, 0 replies; 56+ messages in thread
From: Duncan @ 2014-06-11 4:18 UTC (permalink / raw
To: gentoo-dev
Ryan Hill posted on Tue, 10 Jun 2014 22:10:07 -0600 as excerpted:
[On switching the gentoo tree to git.]
> Weren't we also waiting for some gpg signing stuff to land?
At one point, yes, but AFAIK, that was actually resolved some time ago
(a year, two?) now.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 16:45 ` Andrew Savchenko
2014-06-10 17:09 ` Rich Freeman
@ 2014-06-10 19:58 ` hasufell
2014-06-10 20:36 ` Sergei Trofimovich
2014-06-10 21:32 ` Rich Freeman
2014-06-11 12:59 ` Alexander Berntsen
2 siblings, 2 replies; 56+ messages in thread
From: hasufell @ 2014-06-10 19:58 UTC (permalink / raw
To: gentoo-dev
Andrew Savchenko:
> On Tue, 10 Jun 2014 17:49:15 +0200 Alexander Berntsen wrote:
>> On 10/06/14 17:45, Andrew Savchenko wrote:
>>> I don't know why CVS is still used for Gentoo main repository,
>>> probably some infrastructure elements depends deeply on its
>>> internals, because I see of no other reason why Git is still not
>>> used despite efforts ongoing for last several years.
>> Infra can probably speak for themselves, but Portage with its history
>> is crazy big, and git is not great with crazy big projects.
>
> Why are you saying that git is inefficient with large projects? It
> was developed with efficiency in mind in the first place. And
> kernel guys will likely disagree with "git is not great with crazy
> big projects" statement. And with git kernel bisection and other
> complicated (in terms or data manipulation) operations are quite
> fast even on old hardware.
>
> Best regards,
> Andrew Savchenko
>
interesting read:
http://thread.gmane.org/gmane.comp.version-control.git/189776
Does any1 know what fb currently uses or if any of these issues have
been resolved?
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 19:58 ` [gentoo-dev] " hasufell
@ 2014-06-10 20:36 ` Sergei Trofimovich
2014-06-10 21:32 ` Rich Freeman
1 sibling, 0 replies; 56+ messages in thread
From: Sergei Trofimovich @ 2014-06-10 20:36 UTC (permalink / raw
To: gentoo-dev; +Cc: hasufell
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On Tue, 10 Jun 2014 19:58:36 +0000
hasufell <hasufell@gentoo.org> wrote:
> Andrew Savchenko:
> > On Tue, 10 Jun 2014 17:49:15 +0200 Alexander Berntsen wrote:
> >> On 10/06/14 17:45, Andrew Savchenko wrote:
> >>> I don't know why CVS is still used for Gentoo main repository,
> >>> probably some infrastructure elements depends deeply on its
> >>> internals, because I see of no other reason why Git is still not
> >>> used despite efforts ongoing for last several years.
> >> Infra can probably speak for themselves, but Portage with its history
> >> is crazy big, and git is not great with crazy big projects.
> >
> > Why are you saying that git is inefficient with large projects? It
> > was developed with efficiency in mind in the first place. And
> > kernel guys will likely disagree with "git is not great with crazy
> > big projects" statement. And with git kernel bisection and other
> > complicated (in terms or data manipulation) operations are quite
> > fast even on old hardware.
> >
> > Best regards,
> > Andrew Savchenko
> >
>
> interesting read:
> http://thread.gmane.org/gmane.comp.version-control.git/189776
>
> Does any1 know what fb currently uses or if any of these issues have
> been resolved?
>
Mercurial + custom plugins: https://www.youtube.com/watch?v=Dlguc63cRXg
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 19:58 ` [gentoo-dev] " hasufell
2014-06-10 20:36 ` Sergei Trofimovich
@ 2014-06-10 21:32 ` Rich Freeman
1 sibling, 0 replies; 56+ messages in thread
From: Rich Freeman @ 2014-06-10 21:32 UTC (permalink / raw
To: gentoo-dev
On Tue, Jun 10, 2014 at 3:58 PM, hasufell <hasufell@gentoo.org> wrote:
>
> interesting read:
> http://thread.gmane.org/gmane.comp.version-control.git/189776
>
> Does any1 know what fb currently uses or if any of these issues have
> been resolved?
>
Not sure, but I did a git status on the actual gentoo-x86 converted
repository (all commits) and it took about 30s. It has about 130k
files in it, and I suspect that the number of files matters a good
deal. Git status should need to compare the working tree (a directory
tree) against the index (which is a flat file I think) against the
head (which is a tree full of tree files). The index should perform
very well as the number of files grow, but the tree and head should
become much harder to traverse as the number of subdirectories grow
(assuming the filesystem design requires seeks to navigate to
subdirectories but not to read the contents of a directory).
Our tree isn't all that deep. I'd think the pathological case for git
would be a repository in which there is a single file 1.5M subdirs
deep. That would require 1.5M trees in the repository to store for a
single file, or 1.5M filesystem readdirs to traverse the working tree.
If your repository were flat I'd think that git would perform
reasonably well, though it would still have to compare all those
hashes to find out what changed (but how long can it take a CPU to
compare 1.5M pre-computed hashes?).
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The state and future of the OpenRC project
2014-06-10 16:45 ` Andrew Savchenko
2014-06-10 17:09 ` Rich Freeman
2014-06-10 19:58 ` [gentoo-dev] " hasufell
@ 2014-06-11 12:59 ` Alexander Berntsen
2 siblings, 0 replies; 56+ messages in thread
From: Alexander Berntsen @ 2014-06-11 12:59 UTC (permalink / raw
To: gentoo-dev
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/06/14 18:45, Andrew Savchenko wrote:
> Why are you saying that git is inefficient with large projects?
Because it is.
> It was developed with efficiency in mind in the first place.
Not for big projects.
> And kernel guys will likely disagree with "git is not great with
> crazy big projects" statement
Not the last time I chatted to any of them, nor the last time I saw
Linus say anything about this.
> And with git kernel bisection and other complicated (in terms or
> data manipulation) operations are quite fast even on old hardware.
The Linux repository is nowhere near Portage-big. Rich mentions one of
the reasons. Another is that for Linux, they very carefully decided to
throw away history to make migration easier. I don't think we're about
to throw away history for Portage.
See also the Facebook link Julian posted. As Sergei linked, Facebook
"solved" this by not using git.
Personally I tend to believe that if git can't handle your project,
you are doing something wrong in terms of modularity. But in the "real
world", that's not always amendable.
- --
Alexander
bernalex@gentoo.org
https://secure.plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlOYUrAACgkQRtClrXBQc7XyoQD6AhPbhXqL4D7chnYnNF28+wGK
oy+7MuNwiSgeQRCZk2EBAImLz2m2lEeMLrnGqUR+EKiROo+yWQhWPZ8tqCmB0kPO
=PYpt
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 56+ messages in thread
* [gentoo-dev] The infinite git migration
2014-06-10 15:45 ` Andrew Savchenko
2014-06-10 15:49 ` Alexander Berntsen
@ 2014-06-10 22:59 ` Patrick Lauer
2014-06-10 23:15 ` Rich Freeman
` (2 more replies)
1 sibling, 3 replies; 56+ messages in thread
From: Patrick Lauer @ 2014-06-10 22:59 UTC (permalink / raw
To: gentoo-dev
On 06/10/2014 11:45 PM, Andrew Savchenko wrote:
[lots of whining removed ;) ]
>
> I don't know why CVS is still used for Gentoo main repository,
> probably some infrastructure elements depends deeply on its
> internals, because I see of no other reason why Git is still not
> used despite efforts ongoing for last several years.
>
One part of it: Manpower. Few people have worked on the git migration,
and those are often busy with more important things (like work, life,
other gentoo issues)
Another part: Git wasn't ready.
The first migration attempt failed after consuming nearly 100GB of RAM!
When it did work it took obscene amounts of time, and the result was
unusably large (e.g. initial checkout would take 16GB RAM on the server,
thus not allowing a few hundred devs to do checkouts the same day).
The current state is almost usable, but it is still obscenely slow (e.g.
initial clone taking ~10 CPU-minutes just to figure out what to do), but
we can just throw more hardware at it.
(10 minutes @ 3.6Ghz, so on my notebook it'll take about 4h to just
clone the friggin repository. Too awesome!)
Another part: Few people thought about the difficult problems in the
migration. For example the rsync mirrors, which will still be used - the
scripts that generate those will need to be changed, tested, and then
replaced if a migration ever happens.
If you fix all those you may have a chance, but with the current
performance pessimization I don't see git as viable for nontrivial
repositories. Seriously, I won't wait a few hours for it to clone, even
CVS is faster than that!
So get busy, figure out how to help, then your complaints will not be in
vain :)
Have fun,
Patrick
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-10 22:59 ` [gentoo-dev] The infinite git migration Patrick Lauer
@ 2014-06-10 23:15 ` Rich Freeman
2014-06-11 0:48 ` Duy Nguyen
2014-06-11 12:54 ` Alex Xu
2 siblings, 0 replies; 56+ messages in thread
From: Rich Freeman @ 2014-06-10 23:15 UTC (permalink / raw
To: gentoo-dev
On Tue, Jun 10, 2014 at 6:59 PM, Patrick Lauer <patrick@gentoo.org> wrote:
> The first migration attempt failed after consuming nearly 100GB of RAM!
> When it did work it took obscene amounts of time, and the result was
> unusably large (e.g. initial checkout would take 16GB RAM on the server,
> thus not allowing a few hundred devs to do checkouts the same day).
Well, effort required to do the migration isn't too big of a deal
since it is a one-time event. As long as it can be done correctly, it
is good enough. Ferringb was routinely crunching it in something like
an hour at the end of last year, granted on a system with an obscene
number of cores.
> The current state is almost usable, but it is still obscenely slow (e.g.
> initial clone taking ~10 CPU-minutes just to figure out what to do), but
> we can just throw more hardware at it.
> (10 minutes @ 3.6Ghz, so on my notebook it'll take about 4h to just
> clone the friggin repository. Too awesome!)
Hmm, can't say I've tried it on a variety of systems but I never had
trouble cloning it. You are cloning from a bundle right, and not just
hitting the server for the whole tree, right? The thought is to have
a hook that will block anybody from actually doing a full clone from
the server. Instead users would clone from a bundle (either full or
with shallow history) and then do pulls from the server vs that. The
bundle would just be distributed on the mirrors.
>
> Another part: Few people thought about the difficult problems in the
> migration. For example the rsync mirrors, which will still be used - the
> scripts that generate those will need to be changed, tested, and then
> replaced if a migration ever happens.
Well, I wouldn't say that few have thought about it. The bigger issue
is that I don't think any of the existing code is published anywhere,
so it is a bit hard to contribute to it. If that isn't the case I'm
happy to be corrected.
But, yes, that is the bigger block right now.
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-10 22:59 ` [gentoo-dev] The infinite git migration Patrick Lauer
2014-06-10 23:15 ` Rich Freeman
@ 2014-06-11 0:48 ` Duy Nguyen
2014-06-11 0:55 ` Greg Turner
2014-06-11 9:38 ` Sergey Popov
2014-06-11 12:54 ` Alex Xu
2 siblings, 2 replies; 56+ messages in thread
From: Duy Nguyen @ 2014-06-11 0:48 UTC (permalink / raw
To: gentoo-dev
On Wed, Jun 11, 2014 at 5:59 AM, Patrick Lauer <patrick@gentoo.org> wrote:
> Another part: Git wasn't ready.
> The first migration attempt failed after consuming nearly 100GB of RAM!
> When it did work it took obscene amounts of time, and the result was
> unusably large (e.g. initial checkout would take 16GB RAM on the server,
> thus not allowing a few hundred devs to do checkouts the same day).
> The current state is almost usable, but it is still obscenely slow (e.g.
> initial clone taking ~10 CPU-minutes just to figure out what to do), but
> we can just throw more hardware at it.
> (10 minutes @ 3.6Ghz, so on my notebook it'll take about 4h to just
> clone the friggin repository. Too awesome!)
Since v1.9.0 we can clone from a shallow repository. We can host two
repos on the server: a full repo and a shallow one, containing history
of only last year. Most of the time spent in initial clone is to
verify the history. Shorter history would shorten that time. But you
need to try out to see how long it actually is. I'm not sure if that
16GB includes cloning, or just plain checkout. If the latter, Git has
a problem.
--
Duy
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-11 0:48 ` Duy Nguyen
@ 2014-06-11 0:55 ` Greg Turner
2014-06-11 9:38 ` Sergey Popov
1 sibling, 0 replies; 56+ messages in thread
From: Greg Turner @ 2014-06-11 0:55 UTC (permalink / raw
To: gentoo-dev
On Tue, Jun 10, 2014 at 5:48 PM, Duy Nguyen <pclouds@gmail.com> wrote:
> Since v1.9.0 we can clone from a shallow repository.
Wow, awesome! Thank you, git developers, you rock (and sorry I'm too
lazy to tell you in your own mailing list :) )!
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-11 0:48 ` Duy Nguyen
2014-06-11 0:55 ` Greg Turner
@ 2014-06-11 9:38 ` Sergey Popov
2014-06-11 13:35 ` Duy Nguyen
1 sibling, 1 reply; 56+ messages in thread
From: Sergey Popov @ 2014-06-11 9:38 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]
11.06.2014 04:48, Duy Nguyen пишет:
> On Wed, Jun 11, 2014 at 5:59 AM, Patrick Lauer <patrick@gentoo.org> wrote:
>> Another part: Git wasn't ready.
>> The first migration attempt failed after consuming nearly 100GB of RAM!
>> When it did work it took obscene amounts of time, and the result was
>> unusably large (e.g. initial checkout would take 16GB RAM on the server,
>> thus not allowing a few hundred devs to do checkouts the same day).
>> The current state is almost usable, but it is still obscenely slow (e.g.
>> initial clone taking ~10 CPU-minutes just to figure out what to do), but
>> we can just throw more hardware at it.
>> (10 minutes @ 3.6Ghz, so on my notebook it'll take about 4h to just
>> clone the friggin repository. Too awesome!)
>
> Since v1.9.0 we can clone from a shallow repository. We can host two
> repos on the server: a full repo and a shallow one, containing history
> of only last year. Most of the time spent in initial clone is to
> verify the history. Shorter history would shorten that time. But you
> need to try out to see how long it actually is. I'm not sure if that
> 16GB includes cloning, or just plain checkout. If the latter, Git has
> a problem.
>
Not sure if you can commit into that shallow repo(IIRC, you can not). I
thought shallow clones is more suitable for users that want some state
but do not want the whole history.
--
Best regards, Sergey Popov
Gentoo developer
Gentoo Desktop Effects project lead
Gentoo Qt project lead
Gentoo Proxy maintainers project lead
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-11 9:38 ` Sergey Popov
@ 2014-06-11 13:35 ` Duy Nguyen
0 siblings, 0 replies; 56+ messages in thread
From: Duy Nguyen @ 2014-06-11 13:35 UTC (permalink / raw
To: gentoo-dev
On Wed, Jun 11, 2014 at 4:38 PM, Sergey Popov <pinkbyte@gentoo.org> wrote:
> 11.06.2014 04:48, Duy Nguyen пишет:
>> On Wed, Jun 11, 2014 at 5:59 AM, Patrick Lauer <patrick@gentoo.org> wrote:
>>> Another part: Git wasn't ready.
>>> The first migration attempt failed after consuming nearly 100GB of RAM!
>>> When it did work it took obscene amounts of time, and the result was
>>> unusably large (e.g. initial checkout would take 16GB RAM on the server,
>>> thus not allowing a few hundred devs to do checkouts the same day).
>>> The current state is almost usable, but it is still obscenely slow (e.g.
>>> initial clone taking ~10 CPU-minutes just to figure out what to do), but
>>> we can just throw more hardware at it.
>>> (10 minutes @ 3.6Ghz, so on my notebook it'll take about 4h to just
>>> clone the friggin repository. Too awesome!)
>>
>> Since v1.9.0 we can clone from a shallow repository. We can host two
>> repos on the server: a full repo and a shallow one, containing history
>> of only last year. Most of the time spent in initial clone is to
>> verify the history. Shorter history would shorten that time. But you
>> need to try out to see how long it actually is. I'm not sure if that
>> 16GB includes cloning, or just plain checkout. If the latter, Git has
>> a problem.
>>
>
> Not sure if you can commit into that shallow repo(IIRC, you can not).
Not before v1.9.0. Since 1.9, shallow repos are no different than full
ones. You can fetch from a shallow repo, to a shallow repo, as well as
push from/to a shallow repo.
--
Duy
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-10 22:59 ` [gentoo-dev] The infinite git migration Patrick Lauer
2014-06-10 23:15 ` Rich Freeman
2014-06-11 0:48 ` Duy Nguyen
@ 2014-06-11 12:54 ` Alex Xu
2014-06-11 14:34 ` Rich Freeman
2 siblings, 1 reply; 56+ messages in thread
From: Alex Xu @ 2014-06-11 12:54 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On 10/06/14 06:59 PM, Patrick Lauer wrote:
> [snip]
https://bugs.gentoo.org/show_bug.cgi?id=333531
> The current state is almost usable, but it is still obscenely slow
> (e.g. initial clone taking ~10 CPU-minutes just to figure out what to
> do), but we can just throw more hardware at it.
https://bugs.gentoo.org/show_bug.cgi?id=333685:
> git 2.0 has pack-bitmap apparently :)
so once infra lands that that's basically the end of the major blockers
afaik
On 10/06/14 06:59 PM, Patrick Lauer wrote:
> Another part: Few people thought about the difficult problems in the
> migration. For example the rsync mirrors, which will still be used - the
> scripts that generate those will need to be changed, tested, and then
> replaced if a migration ever happens.
https://bugs.gentoo.org/show_bug.cgi?id=333701:
> What comment #2 should have said: "This bug is so low priority to the
> overall initiative that there shouldn't be anyone considering it a
> blocker, show me the git repo then we can talk" :)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-11 12:54 ` Alex Xu
@ 2014-06-11 14:34 ` Rich Freeman
2014-06-11 18:46 ` Rich Freeman
0 siblings, 1 reply; 56+ messages in thread
From: Rich Freeman @ 2014-06-11 14:34 UTC (permalink / raw
To: gentoo-dev
On Wed, Jun 11, 2014 at 8:54 AM, Alex Xu <alex_y_xu@yahoo.ca> wrote:
>
> https://bugs.gentoo.org/show_bug.cgi?id=333701:
>> What comment #2 should have said: "This bug is so low priority to the
>> overall initiative that there shouldn't be anyone considering it a
>> blocker, show me the git repo then we can talk" :)
>
We have a git repo now. We can generate one at any time. We still
don't have infra tools.
I don't know if the repo is published anywhere, but there are plenty
of bundles on dev.gentoo.org:/space/git-work/
If the infra backend scripts are actually published somewhere where an
outside contributor can work on them and somebody is willing to do so,
I'd be more than happy to push a bundle to github, or post it
somewhere to download.
If people don't want to work on them, fine. This is a volunteer
effort. However, there really isn't any aspect of the git migration
that isn't worth working on. If everybody is just going to sit around
until everybody else does their part of the task, then we might as
well give up now. :)
So, I find stuff like comment #2 unhelpful, but at the same time
nobody is really obligated to help out here. I just think that the
infra components are certainly worth working on.
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread
* Re: [gentoo-dev] The infinite git migration
2014-06-11 14:34 ` Rich Freeman
@ 2014-06-11 18:46 ` Rich Freeman
0 siblings, 0 replies; 56+ messages in thread
From: Rich Freeman @ 2014-06-11 18:46 UTC (permalink / raw
To: gentoo-dev
On Wed, Jun 11, 2014 at 10:34 AM, Rich Freeman <rich0@gentoo.org> wrote:
> We have a git repo now. We can generate one at any time. We still
> don't have infra tools.
>
> I don't know if the repo is published anywhere, but there are plenty
> of bundles on dev.gentoo.org:/space/git-work/
So, if anybody does want to play around with Gentoo in git:
https://github.com/rich0/gentoo-gitmig-2014-02-21.git
This is just a snapshot from Feb.
As a side note, it took about 10min to push to github, then git sat
around waiting to terminate for 7min more before the remote side
dropped the connection. At that point it appeared to have failed, but
a few hours later everything was there. I'm sure the admins over at
github are cursing my name.
We need to get all the migration utility code published as well. My
validation scripts are on github, with instructions on the wiki.
Rich
^ permalink raw reply [flat|nested] 56+ messages in thread