All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Kevin Hickey <khickey@rmicorp.com>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Manuel Lauss <mano@roarinelk.homelinux.net>,
	Linux-MIPS <linux-mips@linux-mips.org>,
	Florian Fainelli <florian@openwrt.org>,
	Bruno Randolf <bruno.randolf@4g-systems.biz>
Subject: Re: [PATCH 2/3] Alchemy: Move evalboard code to common directory
Date: Wed, 12 Nov 2008 15:45:40 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0811121540430.7161@ftp.linux-mips.org> (raw)
In-Reply-To: <1226497082.9026.23.camel@kh-d820-ubuntu.razamicroelectronics.com>

On Wed, 12 Nov 2008, Kevin Hickey wrote:

> > > And in keeping with my other email, I think that the evalboards
> > > directory is a good idea (though I would recommend the name
> > > "develboards" as that is what DB stands for), but it should contain
> > >   
> >    I'd prefer devel-boards, or dev-boards.
> dev-boards works for me.

 FWIW, I'd call it "boards" -- it's shorter, sounds and looks right, no 
question about hyphens and clear.  That is I do hope it is and everybody 
involved will know it's not about wood or directors.

  Maciej

  reply	other threads:[~2008-11-12 15:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08 12:08 [PATCH 0/3] Alchemy: consolidate board code, v2 Manuel Lauss
2008-11-08 12:08 ` [PATCH 1/3] Alchemy: merge small board files into single files Manuel Lauss
2008-11-12  3:54   ` Kevin Hickey
2008-11-12  6:05     ` Manuel Lauss
2008-11-08 12:08 ` [PATCH 2/3] Alchemy: Move evalboard code to common directory Manuel Lauss
2008-11-12  4:00   ` Kevin Hickey
2008-11-12  6:06     ` Manuel Lauss
2008-11-12 10:38       ` Sergei Shtylyov
2008-11-12 10:55         ` Sergei Shtylyov
2008-11-12 10:35     ` Sergei Shtylyov
2008-11-12 12:05       ` Manuel Lauss
2008-11-12 13:39         ` Kevin Hickey
2008-11-12 13:38       ` Kevin Hickey
2008-11-12 15:45         ` Maciej W. Rozycki [this message]
2008-11-12 15:52           ` Sergei Shtylyov
2008-11-12 16:16             ` Maciej W. Rozycki
2008-11-12 16:20               ` Sergei Shtylyov
2008-11-08 12:08 ` [PATCH 3/3] Alchemy: allow boards to override default reset/poweroff functions Manuel Lauss
  -- strict thread matches above, loose matches on Subject: below --
2008-11-07 18:41 [PATCH 0/3] Alchemy: consolidate board code Manuel Lauss
2008-11-07 18:41 ` [PATCH 1/3] Alchemy: merge small board files into single files Manuel Lauss
     [not found]   ` <cover.1226083170.git.mano@roarinelk.homelinux.net>
2008-11-07 18:41     ` [PATCH 2/3] Alchemy: Move evalboard code to common directory Manuel Lauss

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=alpine.LFD.1.10.0811121540430.7161@ftp.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=bruno.randolf@4g-systems.biz \
    --cc=florian@openwrt.org \
    --cc=khickey@rmicorp.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    --cc=sshtylyov@ru.mvista.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 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.