From: Jean Delvare <khali@linux-fr.org>
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Trailing comments in broken-out series file break quilt
Date: Tue, 30 Aug 2005 21:06:38 +0200 [thread overview]
Message-ID: <20050830210638.69d8918d.khali@linux-fr.org> (raw)
In-Reply-To: <20050829191516.4e5d9e0b.pj@sgi.com>
Hi Paul,
> However the quilt command passes these additional terms to the patch
> command as additional arguments, confusing the heck out of patch,
> and generating an error message that confused the heck out of me.
>
> Question - should I be asking Andrew not to comment this way, or
> should I be asking quilt to recognize a comment convention here?
You should simply be using an up-to-date version of quilt, namely
version 0.42, which supports Andrew-style comments in series files just
fine.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2005-08-30 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 2:15 Trailing comments in broken-out series file break quilt Paul Jackson
2005-08-30 3:03 ` Andrew Morton
2005-08-30 8:03 ` Paul Jackson
2005-08-30 19:06 ` Jean Delvare [this message]
2005-08-31 1:39 ` Paul Jackson
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=20050830210638.69d8918d.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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