From: Michael Hope <michael.hope@linaro.org>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: Re: [PATCH] configure: support arbitrary versions via a shell script
Date: Mon, 14 Nov 2011 20:37:00 -0000 [thread overview]
Message-ID: <CANLjY-n2NXdjFhGg2E=GdYsfqcgWKrHGctBGCiN3JvUUVaqRuw@mail.gmail.com> (raw)
In-Reply-To: <201111140820.57656.yann.morin.1998@anciens.enib.fr>
On Mon, Nov 14, 2011 at 8:20 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> Michael, All,
>
> On Monday 14 November 2011 001022 Michael Hope wrote:
>> # HG changeset patch
>> # User Michael Hope <michael.hope@linaro.org>
>> # Date 1321225775 -46800
>> # Branch any-version
>> # Node ID 02572d8009f6a872ccd28d2e020b19772d7e8906
>> # Parent 3cd375ecdd7213104577bbd70863fa35f387bb93
>> configure: support arbitrary versions via a shell script
>
> I already pushed a similar change this WE:
> http://crosstool-ng.org/hg/crosstool-ng/rev/d77d04661cd9
>
> I named the script 'version.sh', without a leading dot.
That sounds good. There's a minor bug in your version: ./configure
--help uses the version from .version instead of version.sh as
do_help() is called before version.sh is updated.
Then again, it had a similar problem before the patch: ./configure
--help would report crosstool-NG-hg instead of the full
crosstool-NG-hg-revno-foo.
Let me know if it's important and I can make a patch,
-- Michael
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-11-14 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 23:10 Michael Hope
2011-11-14 7:21 ` Yann E. MORIN
2011-11-14 20:37 ` Michael Hope [this message]
2011-11-14 21:17 ` Yann E. MORIN
2011-11-15 2:42 ` Michael Hope
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='CANLjY-n2NXdjFhGg2E=GdYsfqcgWKrHGctBGCiN3JvUUVaqRuw@mail.gmail.com' \
--to=michael.hope@linaro.org \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).