From: Stefan Kisdaroczi <kisda@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [announce] Xenomai v2.5.5
Date: Wed, 06 Oct 2010 18:05:55 +0200 [thread overview]
Message-ID: <4CAC9E63.7090407@domain.hid> (raw)
In-Reply-To: <4CAC869E.1010503@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On 06.10.2010 16:24, Gilles Chanteperdrix wrote:
> Stefan Kisdaroczi wrote:
>
>> Hi Gilles,
>>
>> On 06.10.2010 14:05, Gilles Chanteperdrix wrote:
>>
>>> [...]
>>> - the debian patch generation script, which caused invalid patches to be
>>> generated for recent kernel releases
>>>
>>>
>> The file scripts/prepare-patch.sh is missing in the
>> xenomai-2.5.5.tar.bz2 archive.
>>
> I do not see it in scripts/Makefile.am EXTRA_DIST. Did I miss some part
> of your patch?
>
No. I missed that in the patch, I just moved the file from debian/ to
scripts/.
Sorry, but a stupid guy like me simply does not understand why a script
in a git tree needs to be put in a Makefile.am so that it gets put in a
archive from that tree.
If I do "git archive v2.5.5 | bzip2 > ..." it works. The only difference
between the archives is the inclusion of the 3 pdf's in the doc/nodist
dir and the 3 small scripts in scripts/maint directory (and
prepare-patch.sh). The pdf's could be put out of the tree, but simple
solutions and workflows are probably just for stupid people like me.
Stefan (annoyed)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2010-10-06 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 12:05 [Xenomai-core] [announce] Xenomai v2.5.5 Gilles Chanteperdrix
2010-10-06 14:16 ` Stefan Kisdaroczi
2010-10-06 14:24 ` Gilles Chanteperdrix
2010-10-06 16:05 ` Stefan Kisdaroczi [this message]
2010-10-06 16:31 ` Gilles Chanteperdrix
2010-10-10 21:09 ` Gilles Chanteperdrix
2010-10-11 20:27 ` Stefan Kisdaroczi
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=4CAC9E63.7090407@domain.hid \
--to=kisda@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.