A few notes, since I talked with Darren about this earlier.
As one of the people in charge of maintaining the git repo, I would like to avoid having, as Darren suggested, a whole
bunch of -contrib repos. However, maybe I'm missing something here, as I think basic git solves this issue:
Use Case: Tomz has a branch of meta-intel that he has pushed to poky-contrib.git:tomz/foo. dvhart wants to look at it
from his local repo:
git remote add poky-contrib ssh://g...@git.pokylinux.org/poky-contrib.git
git fetch poky-contrib tomz/foo:foo
git checkout foo
The fetch allows a sparse checkout of *just* tomz's branch. No need to download all 75M of poky-contrib which is what
you would do with "git remote update". Git remote update is the wrong way to do this and I'd like to avoid having to
swap infrastructure around when it seems to me that this is just one of those "git being a pain to learn"
-b
On 04/27/2011 07:45 AM, Darren Hart wrote:
On 04/27/2011 12:56 AM, Koen Kooi wrote:
Op 27 apr 2011, om 05:00 heeft Darren Hart het volgende geschreven:
git.yoctoproject.org hosts a number of different repositories, some of
which host limited user contributions (such as poky-contrib). These
repositories are setup and administered by a yoctoproject.org system admin.
As our developer base grows, the need for user creatable git trees also
grows. Eventually, *-contrib isn't going to scale, and neither will the
system admin. There are plenty of available places individuals can
create publicly accessible trees (github, kernel.org, or any number of
similar sites). However, I think it would be beneficial for at least
very active developers to be able to create and destroy trees on a whim,
without having to involve the system admin with each event.
kernel.org provides a git web interface for user created trees. I'd like
to see something similar available at yoctoproject.org in order to
establish single place to go looking for "yocto developer trees". Users
would have to justify their request for a user account and agree to a
terms of use. This has served the Linux kernel community very well. I
think it could do the same for us.
Note: I am not offering to setup such a service or even say that it's
possible with the current resources. I just wanted to throw the idea out
there and see if others have found a similar gap in the development
environment and if this idea would address that gap.
Have you though about setting up a gitorious instance on git.yocto?
I think that is a fantastic idea, it gets my vote.
gitorious++
--
---------------
Elizabeth Flanagan
Yocto Project
Release Engineer
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
