All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: pidge@toganlabs.com, yocto@yoctoproject.org
Cc: joshua.g.lock@intel.com
Subject: Re: [PATCH][yocto-autobuilder] lib/buildsteps.py: fix report creation in nigthly-oecore
Date: Fri, 29 Jul 2016 10:58:04 -0500	[thread overview]
Message-ID: <579B7D0C.1070308@linux.intel.com> (raw)
In-Reply-To: <1469807413.3657.1.camel@toganlabs.com>

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]



On 07/29/2016 10:50 AM, Beth 'pidge' Flanagan wrote:
> On Fri, 2016-07-29 at 10:47 -0500, Aníbal Limón wrote:
>>
>> On 07/29/2016 10:31 AM, Beth 'pidge' Flanagan wrote:
>>>
>>> I'd put this in a try except. What happens with eclipse?
>> At this time we don't support eclipse, i'll add the try except and if
>> fails use "unknown_branch: unknown_revision".
>>
>> 	alimon
>>
> 
> Ah, some of us still build for it! :D Remember, we try to not break
> stuff we still support.

Yes right, may be i don't exaplain correctly this functionality is for
generate error reports the eclipse buildsets are supported but atm don't
have error report functionality, i could add later. :D

	alimon

> 
> -b
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2016-07-29 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 15:10 [PATCH][yocto-autobuilder] lib/buildsteps.py: fix report creation in nigthly-oecore Aníbal Limón
2016-07-29 15:19 ` Aníbal Limón
2016-07-29 15:31 ` Beth 'pidge' Flanagan
2016-07-29 15:47   ` Aníbal Limón
2016-07-29 15:50     ` Beth 'pidge' Flanagan
2016-07-29 15:58       ` Aníbal Limón [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=579B7D0C.1070308@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=joshua.g.lock@intel.com \
    --cc=pidge@toganlabs.com \
    --cc=yocto@yoctoproject.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.