From: "Tim Rühsen" <tim.ruehsen@gmx.de>
To: Jim Meyering <jim@meyering.net>, Bruno Haible <bruno@clisp.org>
Cc: "bug-gnulib@gnu.org List" <bug-gnulib@gnu.org>,
Paul Eggert <eggert@cs.ucla.edu>, Eric Blake <eblake@redhat.com>
Subject: Re: Alpine: useless-if-before-free: Exec format error
Date: Mon, 24 Jun 2019 10:06:14 +0200 [thread overview]
Message-ID: <3cc41b53-191f-7e4c-5694-61595c548b03@gmx.de> (raw)
In-Reply-To: <CA+8g5KF4ORg-KDx2RJA5_TWs+mmCbLgCQ5NgH5Vkgek0uBz_TQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1236 bytes --]
On 6/23/19 6:32 PM, Jim Meyering wrote:
> On Wed, Jun 19, 2019 at 3:12 AM Bruno Haible <bruno@clisp.org> wrote:
> ...
>> Done like this:
>>
>> 2019-06-19 Bruno Haible <bruno@clisp.org>
>>
>> Reorder pieces of header in perl scripts.
>> The desired order is
>> - Prologue part 1 (2 lines with #!)
>> - Program short description
>> - Copyright and license notice
>> - Written-by notice
>> - Program short description (optional)
>> - Program long description (optional)
>> - Prologue part 2
>> - Time stamp
>> - Code
>> Reported by Paul Eggert.
>> * build-aux/announce-gen: Reorder header.
>> * build-aux/gitlog-to-changelog: Likewise.
>> * build-aux/useless-if-before-free: Likewise.
>> * build-aux/prefix-gnulib-mk: Add copyright notice and short
>> description.
>> * build-aux/update-copyright: Likewise. Add short description. Bump
>> time-stamp-line-limit to 200.
>
> Thank you all for improving those scripts!
>
I didn't expect this to escalate so much - and can only repeat what Jim
says, thank you for doing all this work !
Regards, Tim
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-06-24 8:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 17:04 Alpine: useless-if-before-free: Exec format error Tim Rühsen
2019-06-14 17:50 ` Paul Eggert
2019-06-14 19:47 ` Tim Rühsen
2019-06-14 21:28 ` Bruno Haible
2019-06-14 21:47 ` Eric Blake
2019-06-14 23:17 ` Bruno Haible
2019-06-14 23:51 ` Bruno Haible
2019-06-15 0:47 ` Paul Eggert
2019-06-15 2:03 ` Bruno Haible
2019-06-15 7:23 ` Paul Eggert
2019-06-15 11:06 ` Bruno Haible
2019-06-15 11:25 ` Darshit Shah
2019-06-15 12:01 ` Emacs time stamp hook Bruno Haible
2019-06-15 13:39 ` Darshit Shah
2019-06-15 15:25 ` Bruno Haible
2019-06-15 18:35 ` Paul Eggert
2019-06-15 19:48 ` Bruno Haible
2019-06-16 0:30 ` Jim Meyering
2019-06-16 12:57 ` Bruno Haible
2019-06-15 18:35 ` Alpine: useless-if-before-free: Exec format error Paul Eggert
2019-06-15 20:14 ` Bruno Haible
2019-06-15 23:17 ` Paul Eggert
2019-06-16 13:12 ` Bruno Haible
2019-06-18 0:51 ` Paul Eggert
2019-06-18 1:32 ` Bruno Haible
2019-06-18 2:30 ` Paul Eggert
2019-06-19 10:10 ` Bruno Haible
2019-06-23 16:32 ` Jim Meyering
2019-06-24 8:06 ` Tim Rühsen [this message]
2019-06-15 10:41 ` Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3cc41b53-191f-7e4c-5694-61595c548b03@gmx.de \
--to=tim.ruehsen@gmx.de \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eblake@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=jim@meyering.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).