From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: brian avery <brian.avery@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] gen-lockedsig-cache: catch os.link error V2
Date: Fri, 17 Mar 2017 21:32:21 +0000 [thread overview]
Message-ID: <2585804f225c47279417a3859f6cc305@XBOX02.axis.com> (raw)
In-Reply-To: <cover.1489754655.git.brian.avery@intel.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> brian avery
> Sent: den 17 mars 2017 13:50
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] [PATCH 0/1] gen-lockedsig-cache: catch os.link error V2
>
> If your sstate-cache directory is on a different filesystem from the
> one your build is on, gen-lockedsig-cache fails which causes the esdk
> creation to fail. This catches the hard link failure and does a copy in
> those cases.
>
> This is a V2 because I took a copy/paste shortcut when I sent in the
> last one and that went as well as I should have expected. This one is
> sent from the machine it was tested on... My bad :(.
Do not make the "V2" part of the subject, make it part of the PATCH
prefix, e.g.:
[PATCH v2 0/1] gen-lockedsig-cache: catch os.link error
Otherwise it will become part of the commit message where it does not
make any sense (since there obviously is no V1 committed...)
> -brian
//Peter
next prev parent reply other threads:[~2017-03-17 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 12:49 [PATCH 0/1] gen-lockedsig-cache: catch os.link error V2 brian avery
2017-03-17 12:49 ` [PATCH 1/1] " brian avery
2017-03-17 21:32 ` Peter Kjellerstedt [this message]
2017-03-19 17:32 ` [PATCH 0/1] " Brian Avery
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=2585804f225c47279417a3859f6cc305@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=brian.avery@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 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.