On Sun, 2013-06-30 at 23:18 -0700, Michael Halstead wrote:
> On 06/30/2013 10:44 PM, Darren Hart wrote:
> > On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote:
> > > I can change the name shortly. Is there any reason to keep a read-only
> > > copy available at the current location temporaril
Trevor,
I got a hold of Saul and confirmed that you are right. I have been entering
these strings incorrectly for a good while now. I have applied your patch to
the tip of the yocto-docs repository and republished in our development area
for the manuals.
Thanks,
Scott
>-Original Mess
On 06/30/2013 10:44 PM, Darren Hart wrote:
> On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote:
>> I can change the name shortly. Is there any reason to keep a read-only
>> copy available at the current location temporarily?
> Not really. Unless Bruce is using it in some automated scripts
On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote:
> I can change the name shortly. Is there any reason to keep a read-only
> copy available at the current location temporarily?
Not really. Unless Bruce is using it in some automated scripts that need
to be updated.
--
Darren
>
> Michael
I can change the name shortly. Is there any reason to keep a read-only
copy available at the current location temporarily?
Michael Halstead
Yocto Project / Sys Admin
On 06/30/2013 10:19 PM, Rifenbark, Scott M wrote:
> Hi,
>
> I updated the dev-manual section that tells the user what is in this r
Hi,
I updated the dev-manual section that tells the user what is in this repo and
shows an example of cloning it. Nothing changes except for the name, which I
switched to 'meta-yocto-kernel-extras'. To me, it appears that the contents of
the repo still contain the kernel BitBake append files
Trevor,
Ok - Now I am confused. I just looked through a bunch of commits to poky and
the brackets are indeed used. I got this advice from Saul if I remember
correctly a long time ago because I have been doing it this way for a long
time. I will contact him and ask. Likely that it changed a
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
fatal: Refusing to fetch into current branch refs/heads/stage of non-bare
repository
Now updating daily_check database, please wait for a minute..
Now updating pkginfotable,please wait a minute
['Package', 'Version', 'Upver', 'License', 'Section', 'Home', 'Release',
'Depends', 'BugTra
This weekend I brought down the autobuilder to implement the new build
failure email formatter. This *should* provide a bit more detailed
information in a much easier to read format. Please, let me know of
any tweaks people might like to see in the message format.
-b
--
Elizabeth Flanagan
Yocto
11 matches
Mail list logo
