All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jcm@redhat.com>
To: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
Cc: Sergey Vlasov <vsu@altlinux.ru>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	mit-devel@lists.printk.net
Subject: Re: module-init-tools-3.3-pre10 available
Date: Fri, 23 Feb 2007 10:41:54 -0500	[thread overview]
Message-ID: <45DF0B42.2080208@redhat.com> (raw)
In-Reply-To: <20070223120136.12ea11db@home.brethil>

Luiz Fernando N. Capitulino wrote:
> On Thu, 22 Feb 2007 09:52:20 -0500
> Jon Masters <jcm@redhat.com> wrote:
> 
> | Sergey Vlasov wrote:
> | 
> | > I see that you have merged some patches which change depmod.8.
> | > However, this file is generated from doc/depmod.sgml, which was not
> | > changed appropriately.
> | 
> | Ah. A valid point - Luiz, do you want to redo your patch or I can take a 
> | look at the SGML source myself.
> 
>  Urgh, I didn't know that, sorry.
> 
>  I can redo my patch, but shouldn't the manpages be removed from the
> repository then?

I think it's like the configure/Makefile.in situation. These files 
should technically not be in the repo either (and you removed them in 
your tree) but I re-added them because people have an expectation that:

./configure
make

will do something "out of the box". I just need to re-run 
autoconf/automake periodically to keep the files up to date. It's a 
pain, but I'll script that in due course alongside rebuilding the man 
pages - actually, this is probably just a convenient makefile target.

So if you want to redo the patch against those man pages, I'll 
regenerate them prior to pushing the next update. We'll leave it as it 
is until then because the update (IIRC) was just to re-order existing 
content so it's not like we have to push this with urgency.

Jon.

  reply	other threads:[~2007-02-23 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  2:30 module-init-tools-3.3-pre10 available Jon Masters
     [not found] ` <20070222170732.22c1320b.vsu@altlinux.ru>
2007-02-22 14:52   ` Jon Masters
2007-02-23 15:01     ` Luiz Fernando N. Capitulino
2007-02-23 15:41       ` Jon Masters [this message]
2007-02-24 15:26         ` Jan Engelhardt
2007-02-24 16:13           ` Jon Masters
2007-03-20 20:03             ` [mit-devel] " Sergey Vlasov
2007-03-20 20:09               ` Jon Masters
2007-03-22  8:01                 ` Jon Masters
2007-03-20 20:11               ` Luiz Fernando N. Capitulino

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=45DF0B42.2080208@redhat.com \
    --to=jcm@redhat.com \
    --cc=lcapitulino@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mit-devel@lists.printk.net \
    --cc=vsu@altlinux.ru \
    /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.