From: "Peter A. Bigot" <pab@pabigot.com>
To: OE-core <openembedded-core@lists.openembedded.org>
Subject: preferred remotes for git pulls?
Date: Fri, 31 Oct 2014 05:05:37 -0500 [thread overview]
Message-ID: <54535EF1.20202@pabigot.com> (raw)
There are two changes (virtual/bluez and pseudo-no-host-passwd) that I'd
like to rework and propose for master now that it's reopened. Both are
likely to touch multiple files. Previous comments and the wiki how-to
suggest that git-pull is preferred over patchwork-only for multi-patch
changes like this.
I have existing github resources that I could use as the source. Would
that be acceptable to the maintainers?
If using an openembedded-hosted -contrib repository is preferred, what's
the process for getting access? I'd be touching openembedded-core and
meta-openembedded at the least.
Peter
next reply other threads:[~2014-10-31 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 10:05 Peter A. Bigot [this message]
2014-10-31 10:11 ` preferred remotes for git pulls? Paul Eggleton
2014-10-31 10:18 ` Burton, Ross
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=54535EF1.20202@pabigot.com \
--to=pab@pabigot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox