From: Martin Jansa <martin.jansa@gmail.com>
To: markus.lehtonen@linux.intel.com
Cc: openembedded-core@lists.openembedded.org
Subject: marquiz/build-perf/python-rewrite branch in openembedded-core-contrib
Date: Thu, 23 Jun 2016 12:26:03 +0200 [thread overview]
Message-ID: <20160623102603.GB2567@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
Can you please use different branch name for this?
There was marquiz/build-perf branch just few days ago:
OE @ ~/openembedded-core $ git log --pretty=fuller
contrib/marquiz/build-perf
commit 51bd580b2b44636007e698832f585bbd5785ca02
Author: Markus Lehtonen <markus.lehtonen@linux.intel.com>
AuthorDate: Fri May 27 16:53:08 2016 +0300
Commit: Markus Lehtonen <markus.lehtonen@linux.intel.com>
CommitDate: Thu Jun 16 15:31:15 2016 +0300
oe-build-perf-test: print summary of test statuses
Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com>
And now everybody would need to run git remote prune, to remove this
branch in order to fetch new marquiz/build-perf/python-rewrite (where
marquiz/build-perf will serve as a directory - so there cannot be a
branch with the same name here)
Processing openembedded-core: From
git://git.openembedded.org/openembedded-core-contrib
* [new branch] ChenQi/PU-20160623 -> origin/ChenQi/PU-20160623
error: 'refs/remotes/origin/marquiz/build-perf' exists; cannot create
'refs/remotes/origin/marquiz/build-perf/python-rewrite'
! [new branch] marquiz/build-perf/python-rewrite ->
origin/marquiz/build-perf/python-rewrite (unable to update local ref)
error: some local refs could not be updated; try running
'git remote prune origin' to remove any old, conflicting branches
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2016-06-23 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 10:26 Martin Jansa [this message]
2016-06-24 8:46 ` marquiz/build-perf/python-rewrite branch in openembedded-core-contrib 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=20160623102603.GB2567@jama \
--to=martin.jansa@gmail.com \
--cc=markus.lehtonen@linux.intel.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