From: Krzysztof Halasa <khc@pm•waw.pl>
To: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for August 22 (hdlc/wanbook)
Date: Sat, 23 Aug 2008 15:18:34 +0200 [thread overview]
Message-ID: <m3od3jhnth.fsf@maximus.localdomain> (raw)
In-Reply-To: <20080822152059.c83ea19a.randy.dunlap@oracle.com> (Randy Dunlap's message of "Fri\, 22 Aug 2008 15\:20\:59 -0700")
Hi Randy,
Randy Dunlap <randy.dunlap@oracle•com> writes:
> wanbook.tmpl was removed!?! why?
> Is there some replacement for it or is it just not useful?
The latter. wanbook.tmpl was actually syncppp description only, and
syncppp doesn't seem to be surviving.
> I seem to have missed the patch(es) that did this...
http://lkml.org/lkml/2008/8/9/130
> Looks like Documentation/DocBook/Makefile was missed in the patch.
Precisely. Thanks for the info. Fixed now.
--
Krzysztof Halasa
prev parent reply other threads:[~2008-08-23 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 7:34 linux-next: Tree for August 22 Stephen Rothwell
2008-08-22 22:20 ` linux-next: Tree for August 22 (hdlc/wanbook) Randy Dunlap
2008-08-23 13:18 ` Krzysztof Halasa [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=m3od3jhnth.fsf@maximus.localdomain \
--to=khc@pm$(echo .)waw.pl \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=randy.dunlap@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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