From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@lists.osdl.org
Subject: [KJ] make pdfdocs broken in 2.6.19rc2 and needs fixes
Date: Sun, 22 Oct 2006 21:47:42 +0000 [thread overview]
Message-ID: <200610222347.42418.ak@suse.de> (raw)
When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
messages and then some corrupted PDFs in the end.
Fixing that (I suppose it will just need comment fixes and
should not affect the code) should be a relatively easy task for
a newbie and would be useful for the 2.6.19 release.
-Andi
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: linux-kernel@vger.kernel.org
Cc: kernel-janitors@lists.osdl.org
Subject: make pdfdocs broken in 2.6.19rc2 and needs fixes
Date: Sun, 22 Oct 2006 23:47:42 +0200 [thread overview]
Message-ID: <200610222347.42418.ak@suse.de> (raw)
When you do make pdfdocs with 2.6.19rc2-git7 you get tons of error
messages and then some corrupted PDFs in the end.
Fixing that (I suppose it will just need comment fixes and
should not affect the code) should be a relatively easy task for
a newbie and would be useful for the 2.6.19 release.
-Andi
next reply other threads:[~2006-10-22 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 21:47 Andi Kleen [this message]
2006-10-22 21:47 ` make pdfdocs broken in 2.6.19rc2 and needs fixes Andi Kleen
2006-10-22 22:00 ` [KJ] " Jeff Garzik
2006-10-22 22:00 ` Jeff Garzik
2006-10-22 22:16 ` [KJ] " Randy Dunlap
2006-10-22 22:16 ` Randy Dunlap
2006-10-22 22:30 ` [KJ] " Randy Dunlap
2006-10-22 22:30 ` Randy Dunlap
2006-10-22 22:17 ` Andi Kleen
2006-10-22 22:17 ` Andi Kleen
2006-10-23 11:09 ` [KJ] " Alan Cox
2006-10-23 11:09 ` Alan Cox
2006-10-23 15:49 ` [KJ] " Randy Dunlap
2006-10-23 15:49 ` Randy Dunlap
2006-10-26 19:45 ` walter harms
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=200610222347.42418.ak@suse.de \
--to=ak@suse.de \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-kernel@vger.kernel.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.