From: Mark Hatle <mark.hatle@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: User repos on openemebdded-core-contrib
Date: Tue, 15 Mar 2011 21:10:19 -0500 [thread overview]
Message-ID: <4D801C0B.1040809@windriver.com> (raw)
In-Reply-To: <20110316015133.GA7694@sakrah.homelinux.org>
On 3/15/11 8:51 PM, Khem Raj wrote:
> Hi
>
> The policies on openembedded-core-contrib repo right now does not allow
> me to either delete or do a git push -f on the branches I have pushed
> for pull requests.
>
> The problem becomes suppose when you have feedback on a pull request
> and you do version 2 of the patch and subsequent versions then with
> current policies we will have to create separate branches for each
> request. I thought it would be better if one could delete/rewrite his
> own branches on the contrib repo.
>
> How does yocto manage the contrib repo in this regard?
The yocto project allows push -f's for the contrib repository.
--Mark
> Thoughts?
>
next prev parent reply other threads:[~2011-03-16 3:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 1:51 User repos on openemebdded-core-contrib Khem Raj
2011-03-16 2:10 ` Mark Hatle [this message]
2011-03-16 6:55 ` 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=4D801C0B.1040809@windriver.com \
--to=mark.hatle@windriver.com \
--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.