From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Shortened git hashes causing pain
Date: Thu, 23 May 2013 23:52:29 +0100 [thread overview]
Message-ID: <1369349549.14887.47.camel@ted> (raw)
In-Reply-To: <519E359B.2010203@mlbassoc.com>
On Thu, 2013-05-23 at 09:28 -0600, Gary Thomas wrote:
> The shortening of the git hashes in this commit
> commit 77fc40a0f843e2488b356d90b64ef436c11c9973
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Sun May 19 13:21:55 2013 +0300
> bitbake: fetch2: Shorten long srcrevs
> is causing some problems.
>
> I have a simple .bbappend for gtk-sato-engine (attached) which
> just applies a one-line patch. When I build this recipe, I
> get two different work trees (this is from scratch):
> $ ls -l tmp/work/cobra4430p82-amltd-linux-gnueabi/gtk-sato-engine
> total 8
> drwxrwxr-x 3 gthomas gthomas 4096 May 23 09:12 0.3.3+gitAUTOINC+4740ad8d53aba4368ce3e03b06cfdc69eb86dcdc-r0
> drwxrwxr-x 11 gthomas gthomas 4096 May 23 09:13 0.3.3+gitAUTOINC+4740ad8d53-r0
>
> Note: it doesn't seem to happen for the virgin gtk-sato-engine
> recipe, only when my patch is applied.
Try moving the cache directory in tmp/ out the way. I suspect some kind
of caching issue since there should not be two work directories. What is
the contents of each?
Cheers,
Richard
next prev parent reply other threads:[~2013-05-23 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 15:28 Shortened git hashes causing pain Gary Thomas
2013-05-23 22:52 ` Richard Purdie [this message]
2013-05-23 23:31 ` Gary Thomas
2013-05-23 23:04 ` Gary Thomas
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=1369349549.14887.47.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.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