From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Restore .git directory in git package downloads
Date: Wed, 19 Apr 2017 22:11:03 +0200 [thread overview]
Message-ID: <c271bc4a-498b-dd3a-1554-ee9fbcbbfac9@mind.be> (raw)
In-Reply-To: <a767627c-ac45-d05d-f71b-05a2ea1550d9@andin.de>
On 19-04-17 16:39, Andreas Naumann wrote:
> Hi,
>
> Am 19.04.2017 um 15:01 schrieb Jan Kundr?t:
>> On st?eda 19. dubna 2017 6:15:53 CEST, Baruch Siach wrote:
>>> Is there anything missing for your use case?
>>
>> This is largely hypothetical (I don't know if any of these are packaged
>> for Buldroot), but I know several projects which try to look at the
>> output of `git describe` to create a pretty version string at build time
>> (such as "v0.7-220-g270d875").
>
> For me, a custom kernel from private git repo being is one such project. Right
> now I have a hack to append the shortened contents of
> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION via .scmversion. But of course this is not
> the same/as nice as what git describe or setlocalversion reports.
Cfr. http://patchwork.ozlabs.org/patch/732304/ and subsequent discussion.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-04-19 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 4:00 [Buildroot] [PATCH] Restore .git directory in git package downloads James Balean
2017-04-19 4:15 ` Baruch Siach
2017-04-19 13:01 ` Jan Kundrát
2017-04-19 14:39 ` Andreas Naumann
2017-04-19 20:11 ` Arnout Vandecappelle [this message]
2017-04-19 23:37 ` Ricardo Martincoski
[not found] ` <58f7f1456cc7e_21d33f8c269493f44696f@ultri3.mail>
2017-04-20 3:40 ` Baruch Siach
2017-04-26 3:52 ` James Balean
2017-04-26 4:10 ` Baruch Siach
2017-04-27 17:52 ` Ricardo Martincoski
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=c271bc4a-498b-dd3a-1554-ee9fbcbbfac9@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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