From: Darren Hart <dvhart@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] rt-tests: Add src/backfire to FILES_${PN}
Date: Thu, 15 Mar 2012 22:32:40 -0700 [thread overview]
Message-ID: <4F62D078.1090902@linux.intel.com> (raw)
In-Reply-To: <4F62B50C.5030008@linux.intel.com>
On 03/15/2012 08:35 PM, Saul Wold wrote:
> On 03/15/2012 03:00 PM, Darren Hart wrote:
>> The following changes since commit d4f1ef6b8297826230a68e535098709d07de1f48:
>>
>> qt4: package static libraries correctly to fix warnings (2012-03-15 13:33:37 +0000)
>>
>> are available in the git repository at:
>> git://git.yoctoproject.org/user-contrib/dvhart/oe-core dvhart/updates
>> http://git.yoctoproject.org/cgit.cgi/user-contrib/dvhart/oe-core/log/?h=dvhart/updates
>>
> Not sure what's going on here, but this is always harder for me to get
> to then the standard contrib branches.
>
> It turns out it really dvhart/dvhart/updates, not dvhart/updates
No, the branch is dvhart/updates:
$ git clone git://git.yoctoproject.org/user-contrib/dvhart/oe-core -b dvhart/updates
$ cd oe-core
$ git show HEAD
commit 5ca651eb19c3fcb64de2ce405de0bc7fa2a8c90b
Author: Darren Hart <dvhart@linux.intel.com>
Date: Thu Mar 15 14:51:22 2012 -0700
rt-tests: Add src/backfire to FILES_${PN}
...
So I wonder what you are seeing? Maybe you call the new remote "dvhart" ?
If so, then yes, you would refer to the commit as remote/branch which would
be dvhart/dvhart/updates. So yeah, I don't need the dvhart in the branch
name since this is a personal repo... just an old habit.
I also see that I haven't got this made public yet. I'll fix that.
--
Darren
>
> Sau!
>
>> Darren Hart (1):
>> rt-tests: Add src/backfire to FILES_${PN}
>>
>> meta/recipes-rt/rt-tests/rt-tests_0.83.bb | 3 +++
>> 1 files changed, 3 insertions(+), 0 deletions(-)
>>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2012-03-16 5:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 22:00 [PATCH 0/1] rt-tests: Add src/backfire to FILES_${PN} Darren Hart
2012-03-15 22:00 ` [PATCH 1/1] " Darren Hart
2012-03-16 15:33 ` Darren Hart
2012-03-16 15:55 ` Darren Hart
2012-03-16 16:26 ` Richard Purdie
2012-03-16 16:28 ` Darren Hart
2012-03-16 17:11 ` Richard Purdie
2012-03-16 17:59 ` Darren Hart
2012-03-16 16:06 ` Saul Wold
2012-03-16 16:16 ` Darren Hart
2012-03-16 16:24 ` Richard Purdie
2012-03-16 3:35 ` [PATCH 0/1] " Saul Wold
2012-03-16 5:32 ` Darren Hart [this message]
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=4F62D078.1090902@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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