From: Jonathan Corbet <corbet@lwn.net>
To: Michal Marek <mmarek@suse.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DocBook: Do not exceed argument list limit
Date: Wed, 28 Jan 2015 12:00:33 -0700 [thread overview]
Message-ID: <20150128120033.5c1fe43f@lwn.net> (raw)
In-Reply-To: <1422268277-5333-1-git-send-email-mmarek@suse.cz>
On Mon, 26 Jan 2015 11:31:17 +0100
Michal Marek <mmarek@suse.cz> wrote:
> Use find + xargs to compress the generated manpages. Without this patch,
> the build can fail with
>
> gzip -f Documentation/DocBook/man/*.9
> /bin/bash: /usr/bin/gzip: Argument list too long
That is a lot of files in that directory these days...applied to the docs
tree, thanks.
jon
prev parent reply other threads:[~2015-01-29 1:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 10:31 [PATCH] DocBook: Do not exceed argument list limit Michal Marek
2015-01-27 1:36 ` Randy Dunlap
2015-01-28 19:00 ` Jonathan Corbet [this message]
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=20150128120033.5c1fe43f@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox