From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org, hongxu.jia@windriver.com
Subject: meta-openembedded git repo in some of the openembedded-core-contrib branches
Date: Tue, 11 Jun 2019 22:01:58 +0200 [thread overview]
Message-ID: <20190611200158.GA1858@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
Hi,
when accidentally checking for some old meta-oe commit in oe-core
repository I was surprised that it was found in some of the contrib
branches:
~/openembedded-core $ git branch -a --contains 30bbde3d09e
remotes/contrib/hongxu/add-recipes-20190215
remotes/contrib/hongxu/dbg-split
remotes/contrib/hongxu/misc-fixes
These branches are actually from meta-oe repo, not oe-core.
Please remove old irrelevant branches from -contrib repositories:
https://git.openembedded.org/openembedded-core-contrib/
https://git.openembedded.org/meta-openembedded-contrib/
and make sure you're pushing to the right remote :), it unnecessary
almost doubles the repo size.
Cheers,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next reply other threads:[~2019-06-11 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 20:01 Martin Jansa [this message]
2019-06-12 1:34 ` meta-openembedded git repo in some of the openembedded-core-contrib branches Hongxu Jia
2019-06-12 7:37 ` Martin Jansa
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=20190611200158.GA1858@jama \
--to=martin.jansa@gmail.com \
--cc=hongxu.jia@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.