All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Pull request with misc changes
Date: Tue, 10 May 2011 16:15:10 -0300	[thread overview]
Message-ID: <BANLkTinT7bN=-QfQg24GtrOaRW4U3vv-zQ@mail.gmail.com> (raw)
In-Reply-To: <1305054238.30391.283.camel@rex>

On Tue, May 10, 2011 at 16:03, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>> Hmmm.  I'm going to take a stab at making this a create-pull-request
>> option...
>
> Martin/Tom: Serious question - why not use the contrib repo for this?
>
> I have nightmares about all the development being spread to all the
> corners of the globe and people not being able to see what is being
> worked on. For short lived branches its not so much of a problem but as
> we take on longer lived feature development it will be a problem. I'd
> therefore like to understand why the dislike of it...

Welcome to Distribute Source Control Management World; this is the
beauty of it and I see no reason to restrict or enforce people to use
a repository.

In my personal case we have been using GitHub as a central place to
put projects that O.S. Systems is contributing and this is good to
gather us some visibility so OE will be there too.

So I won't use contrib to share patches. I can send them to mailing
list (as I have been doing). A merge on a topic branch is a git pull
command from you so I see not much problem for you or whom is doing
the pull job.

As an example:

 git checkout -b otavio-20110510-review
 git pull git://github.com/OSSystems/oe-core.git master
 git shortlog origin/master..

Is that so difficult?


-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br



  reply	other threads:[~2011-05-10 19:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 19:15 Pull request with misc changes Otavio Salvador
2011-05-10  5:17 ` Saul Wold
2011-05-10 12:53   ` Otavio Salvador
2011-05-10 18:00     ` Saul Wold
2011-05-10 18:13       ` Martin Jansa
2011-05-10 18:33         ` Tom Rini
2011-05-10 19:03           ` Richard Purdie
2011-05-10 19:15             ` Otavio Salvador [this message]
2011-05-10 19:32               ` Richard Purdie
2011-05-10 19:36               ` Chris Larson
2011-05-10 20:24             ` Martin Jansa
2011-05-10 21:31               ` Koen Kooi
2011-05-11  9:17               ` Richard Purdie
2011-05-11 10:06                 ` Koen Kooi
2011-05-10 18:20       ` Otavio Salvador
2011-05-11  5:39         ` Darren Hart

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='BANLkTinT7bN=-QfQg24GtrOaRW4U3vv-zQ@mail.gmail.com' \
    --to=otavio@ossystems.com.br \
    --cc=openembedded-core@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.