public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Rob Landley <rob@landley.net>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Roland Dreier <rdreier@cisco.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-doc@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] Group architecture Documentation under Documentation/arch.
Date: Sun, 5 Aug 2007 08:39:11 +0900	[thread overview]
Message-ID: <20070804233911.GA29364@linux-sh.org> (raw)
In-Reply-To: <200708041433.30450.rob@landley.net>

On Sat, Aug 04, 2007 at 03:33:29PM -0400, Rob Landley wrote:
> On Saturday 04 August 2007 2:24:46 pm Jesper Juhl wrote:
> > On 04/08/07, Rob Landley <rob@landley.net> wrote:
> > > On Saturday 04 August 2007 2:07:31 pm Jesper Juhl wrote:
> > > > On 04/08/07, Rob Landley <rob@landley.net> wrote:
> > > > > Signed-off-by: Rob Landley <rob@landley.net>
> > > > > Amiga part Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > > > >
> > > > > Move architecture-specific Documentation into a common subdirectory.
> > > >
> > > > ...
> > > >
> > > > I have only one complaint; I don't see an update to
> > > > Documentation/00-INDEX
> > >
> > > I now have at least three.  (I missed blackfin, which wasn't there last
> > > time I did this.)
> >
> > I'm not talking about Documentation/<arch>/00-INDEX, but the 00-INDEX
> > file in the top-level Documentation directory.
> >
> > Or am I misunderstanding you?
> 
> I now have at least three complaints about the patch I just submitted: Your 
> complaint is valid, the empty directories all the files were moved out of 
> don't seem to be deleted when I use git to apply this patch, and I didn't 
> move the blackfin directory into arch because it wasn't there when I 
> initially did this patch.

There's also the single file entries that are tightly coupled to an
architecture to consider as well. Both sgi-visws.txt and voyager.txt
should be consolidated with the i386 stuff, for example.

  reply	other threads:[~2007-08-04 23:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  2:25 Cleaning up the Documentation directory Rob Landley
2007-05-23  2:38 ` Roland Dreier
2007-05-23  4:25   ` [PATCH] " Rob Landley
2007-05-23  4:56     ` Paul Mundt
2007-05-23  6:58       ` Rob Landley
2007-05-23  7:24     ` Geert Uytterhoeven
2007-05-23 15:15       ` Rob Landley
2007-05-31  7:02       ` Rob Landley
2007-05-31  7:04       ` [PATCH 1/2] Group architecture Documentation under Documentation/arch Rob Landley
2007-05-31  7:07       ` [PATCH 2/2] Group multiport serial card documentation under Documentation/serial Rob Landley
2007-08-04 19:03       ` [PATCH 1/2] Group architecture Documentation under Documentation/arch Rob Landley
2007-08-04 19:07         ` Jesper Juhl
2007-08-04 19:22           ` Rob Landley
2007-08-04 19:24             ` Jesper Juhl
2007-08-04 19:33               ` Rob Landley
2007-08-04 23:39                 ` Paul Mundt [this message]
2007-08-04 19:19         ` Rob Landley
2007-08-04 19:34           ` david
2007-08-04 19:05       ` [PATCH 2/2] Group multiport serial card documentation under Documentation/serial Rob Landley
2007-08-04 19:15         ` Jesper Juhl

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=20070804233911.GA29364@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    --cc=rob@landley.net \
    /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