From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] km/common: add toolchain variable
Date: Mon, 19 Dec 2011 13:58:52 +0100 [thread overview]
Message-ID: <4EEF350C.4040501@keymile.com> (raw)
In-Reply-To: <20111219113338.C14CB135A9A2@gemini.denx.de>
Hi Wolfgang,
On 12/19/2011 12:33 PM, Wolfgang Denk wrote:
> In message <4EEF13D4.5020304@keymile.com> you wrote:
>>
>>> You can insert such information when you export the files from git,
>>> say by adding a line like:
>>>
>>> Last commit date: $Format:%H %cD$
> ...
>> After reading the doc I don't know how it could be used in my usecase. Please
>> correct me if I am wrong, but this does only work in combination with the "git
>> archive" command. And I don't want to do an archive, I want to export/copy some
>> files out of the git tree into /tftpboot.
>
> You could for example use the following command to copy this file into
> /tftpboot:
>
> $ cd board/keymile/scripts
> $ git archive --format=tar HEAD README | \
> ( cd /tftpboot ; tar -xpvf - )
>
hm together with the needed git configuration IMO a bit to complicated for my
needs. To be honest I would like to keep this date information as it is.
If this is not acceptable then I will remove this string completely from the
u-boot tree and force the users to add a VERSION file to /tftpboot/scripts with:
$ git describe > /tftpboot/scripts/VERSION
or I keep it as a OOT patch. Just let me know.
Best regards
Holger
next prev parent reply other threads:[~2011-12-19 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 16:11 [U-Boot] [PATCH] km/common: add toolchain variable Holger Brunck
2011-12-17 20:49 ` Wolfgang Denk
2011-12-19 8:07 ` Holger Brunck
2011-12-19 8:57 ` Wolfgang Denk
2011-12-19 10:37 ` Holger Brunck
2011-12-19 11:33 ` Wolfgang Denk
2011-12-19 12:58 ` Holger Brunck [this message]
2011-12-19 15:30 ` Wolfgang Denk
2011-12-20 22:44 ` Wolfgang Denk
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=4EEF350C.4040501@keymile.com \
--to=holger.brunck@keymile.com \
--cc=u-boot@lists.denx.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