From: Jeff Horn <jeff@everlook.net>
To: ptxdist@pengutronix.de
Subject: [ptxdist] UBIFS generation question
Date: Thu, 1 Nov 2012 11:22:36 -0700 [thread overview]
Message-ID: <CAM7q1LmRPVvme726Se3ZX5NGsRBad_N_u=GevTczXOiwo1QegQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 644 bytes --]
Hi,
I currently add the git commit to my BSP by adding this to a custom overlay
rule.
echo $(shell git rev-parse --verify HEAD) > $(ROOTDIR)/etc/revision
That works fine for creating the file in the platform/root directory. When
I started to use the UBI image I noticed that file was missing from my root
filesystem. I see that the ubi.make script does a targetinstall to
platform/images/working_dir and then generates the UBI image from there.
Which obviously does not have my revision. How can I fix/modify my line
above so it makes it into both the root directory and the UBI image.
I'm on ptxdist-2011.07.0
Thanks in advance,
Jeff
[-- Attachment #1.2: Type: text/html, Size: 790 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2012-11-01 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 18:22 Jeff Horn [this message]
2012-11-01 20:37 ` Alexander Dahl
2012-11-02 2:33 ` Jeff Horn
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='CAM7q1LmRPVvme726Se3ZX5NGsRBad_N_u=GevTczXOiwo1QegQ@mail.gmail.com' \
--to=jeff@everlook.net \
--cc=ptxdist@pengutronix.de \
/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