Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE git repository organization
Date: Wed, 22 Dec 2010 11:46:38 +0100	[thread overview]
Message-ID: <4D11D70E.8050104@gmail.com> (raw)
In-Reply-To: <AANLkTin7=Y-zTioQWoMegS4pU3McHnORx-jC+z6petZ-@mail.gmail.com>

Cliff Brake ha scritto, Il 21/12/2010 22:53:
> Now that we have the capability to do per branch permissions, etc, I
> would like to discuss what makes sense going forward for repository
> admin.  My initial thoughts:
> 
> - put all user branches in openembedded-user
> - restrict branch creation on the main openembedded repo to commonly
> used branches
> 
> We can also do things like give users permission to branches that
> start with their name, etc.  This would allow rewriting history on
> user branches, etc.  That said, it may make more sense to just do user
> branches on github as some are already doing.
> 
> Thanks,
> Cliff
> 

Fine

/marco



      parent reply	other threads:[~2010-12-22 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 21:53 OE git repository organization Cliff Brake
2010-12-21 22:12 ` Chris Larson
2010-12-21 22:29   ` Khem Raj
2010-12-22 10:46 ` Marco Cavallini [this message]

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=4D11D70E.8050104@gmail.com \
    --to=koansoftware@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox