From: Theodore Tso <tytso@mit.edu>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [E2FSPROGS, PATCH] Fix "make docs" rule in Makefile for doc folder.
Date: Sun, 13 Apr 2008 17:21:26 -0400 [thread overview]
Message-ID: <20080413212126.GA18156@mit.edu> (raw)
In-Reply-To: <ea11fea30804101255g4d4c772eh2016563954802713@mail.gmail.com>
On Fri, Apr 11, 2008 at 01:25:47AM +0530, Manish Katiyar wrote:
> On systems which don't have makeinfo installed by default, "make" or
> "make docs" fails with the following error
> /home/mkatiyar/e2fs-git> make docs
> make[1]: Entering directory `/home/mkatiyar/e2fs-git/doc'
> MAKEINFO libext2fs.info
> make[1]: makeinfo: Command not found
> make[1]: [libext2fs.info] Error 127 (ignored)
>
> This patch makes it to bail out with proper error message when
> makeinfo is not present.
Can you send me a Signed-off-by for your patch, per the
SUBMITTING-PATCHES file in the e2fsprogs sources?
Many thanks,
- Ted
next prev parent reply other threads:[~2008-04-14 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 19:55 [E2FSPROGS, PATCH] Fix "make docs" rule in Makefile for doc folder Manish Katiyar
2008-04-13 21:21 ` Theodore Tso [this message]
2008-04-14 11:50 ` Manish Katiyar
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=20080413212126.GA18156@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=mkatiyar@gmail.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