All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Larson <clarson@kergoth.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] meta-openembedded layer for yocto hosted on oe.org
Date: Tue, 21 Dec 2010 13:39:23 -0700	[thread overview]
Message-ID: <AANLkTin8BiwPE+hOGrV5tL3NFWH0H=ADKATxOyi3fb85@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=NMydMgVW4GF10we=_csy+gtpncR-5Dq4vmVJc@mail.gmail.com>

On Tue, Dec 21, 2010 at 12:25 PM, Cliff Brake <cliff.brake@gmail.com> wrote:
> On Tue, Dec 21, 2010 at 1:48 PM, Tom Rini <tom_rini@mentor.com> wrote:
>
>>> yes this is something what we should do. We need to setup gitolite on
>>> the git server
>>
>> Can I just put in my 2 cents for some github love?  Chris got me started
>> using it and I'm quite happy.  It'd also be less admin work and since I
>> forked Chris' tree, my space usage is still practically nil (I'm not sure
>> about his), so the free accounts are fine.
>
> I'm sure our gitserver will never compare to github in features, but
> it seems like there is a fundamental limit in that github cannot
> possible host every git repo on the planet, especially for larger
> projects like OE where you have a lot of people pulling.  I think
> there is some value in:

Like Tom says, each user has a limit of what they can store with a
free account.  Any single git repository doesn't take much space.
When someone wants to do some personal work, they fork the upstream
repo into theirs (so they now have a single copy of the oe repository
in their account), and they work there.  I don't think space is much
of a concern.  The other points, about branding, etc are valid.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics



  reply	other threads:[~2010-12-21 20:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 15:53 [RFC] meta-openembedded layer for yocto hosted on oe.org Koen Kooi
2010-12-20 16:56 ` Graeme Gregory
2010-12-20 17:16   ` Frans Meulenbroeks
2010-12-20 19:25     ` Maupin, Chase
2010-12-20 20:31       ` Frans Meulenbroeks
2010-12-21  8:16     ` Koen Kooi
2010-12-21 17:51       ` Frans Meulenbroeks
2010-12-21 18:41         ` Khem Raj
2010-12-21 20:28         ` Marcin Juszkiewicz
2010-12-21 21:16           ` Frans Meulenbroeks
2011-01-02 11:29           ` Frans Meulenbroeks
2010-12-22  5:43         ` Esben Haabendal
2010-12-21  9:45 ` Khem Raj
2010-12-21 18:48   ` Tom Rini
2010-12-21 19:25     ` Cliff Brake
2010-12-21 20:39       ` Chris Larson [this message]
2010-12-21 15:43 ` Cliff Brake
2010-12-21 16:25   ` Koen Kooi
2010-12-21 21:03     ` Denys Dmytriyenko
2010-12-22 11:19 ` Koen Kooi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTin8BiwPE+hOGrV5tL3NFWH0H=ADKATxOyi3fb85@mail.gmail.com' \
    --to=clarson@kergoth.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.