All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM: Summary of 'OE and Poky', 'Hosting', 'Bugtracker'
Date: Tue, 10 Nov 2009 16:52:36 +0100	[thread overview]
Message-ID: <1257868356.5472.1.camel@opal> (raw)
In-Reply-To: <20091110151412.GF3998@excalibur.local>

Am Dienstag, den 10.11.2009, 16:14 +0100 schrieb Stefan Schmidt:
> > Access control: Having user branches in a dedicated tree means we can
> > give more users commit access so that they can prepare branches we can
> > pull. This might lead to (IMHO much appreciated) improvements in the
> > development model towards a pull model.
> 
> But why the hassle of administrate an own git repo service for this? I always
> thought OE was small on admin power.

Sorry, this might have been unclear on my part, it's just different
projects on the same repository, not different repositories. We'd like
to and recommend OE developers to host their branch in a 'contrib'
project on git.oe.org.

Cheers,

:M:





  parent reply	other threads:[~2009-11-10 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 13:07 OEDEM: Summary of 'OE and Poky', 'Hosting', 'Bugtracker' Michael 'Mickey' Lauer
2009-11-10 13:27 ` Stefan Schmidt
2009-11-10 14:35   ` Esben Haabendal
2009-11-10 15:09     ` Stefan Schmidt
2009-11-10 14:38   ` Otavio Salvador
2009-11-10 15:06     ` Esben Haabendal
2009-11-10 14:50   ` Michael 'Mickey' Lauer
2009-11-10 15:14     ` Stefan Schmidt
2009-11-10 15:38       ` Richard Purdie
2009-11-10 15:54         ` Stefan Schmidt
2009-11-10 15:52       ` Michael 'Mickey' Lauer [this message]
     [not found]         ` <be7a9f3d0911100914o45d3526fufb4338966b9cdc33@mail.gmail.com>
2009-11-10 17:19           ` Otavio Salvador
2009-11-10 18:35             ` Esben Haabendal
2009-11-11  1:07 ` Holger Hans Peter Freyther
2009-11-11  8:29   ` Phil Blundell

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=1257868356.5472.1.camel@opal \
    --to=mickey@vanille-media.de \
    --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.