public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Foster <brian.foster@maxim-ic.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v2 9/9] faq: general: add bug reporting FAQ
Date: Wed, 10 Aug 2011 09:54:11 +0200	[thread overview]
Message-ID: <201108100954.11266.brian.foster@maxim-ic.com> (raw)
In-Reply-To: <1312927531-16853-1-git-send-email-computersforpeace@gmail.com>

On Wednesday 10 August 2011 00:05:31 Brian Norris wrote:
> It's surprising to note that we do not have a general "how to send a bug
> report" FAQ. This patch provides a starting point and (most importantly)
> directs UBI/UBIFS users to the appropriate bug reporting information.
> 
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> ---
> v2: handle some of Brian Foster's suggestions regarding clarity, other
>     additions to FAQ entry
> 
>  faq/general.xml |   64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  mail.xml        |    4 ++-
>  2 files changed, 67 insertions(+), 1 deletions(-)
> 
> diff --git a/faq/general.xml b/faq/general.xml
>[...] 
> +	<LI>include information about flash parameters found from
> +	"<CODE>mtdinfo&amp;nbsp;-a</CODE>" (or the less useful info from
> +	"<CODE>cat&amp;nbsp;/proc/mtd</CODE>");</LI>

 ‘&amp;nbsp;’?  I assume that's because this appears to be
 XML which, I also assume, is translated(?) into (X)HTML ?
 (Just checking that that is intended/intentional.)
cheers!
	-blf-
-- 
Brian FOSTER
Principal MTS, Software
Maxim Integrated Products (Microcontroller BU), formerly Innova Card
Web    : http://www.maxim-ic.com/

  reply	other threads:[~2011-08-10  7:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 19:37 [PATCH 0/9] mtd-www: various fixes, bug reporting info Brian Norris
2011-08-08 19:37 ` [PATCH 1/9] UBIFS FAQ: spelling, grammar Brian Norris
2011-08-08 19:37 ` [PATCH 2/9] faq: general: update "pleonasm" description Brian Norris
2011-08-08 19:37 ` [PATCH 3/9] faq: general: turn statement into a question Brian Norris
2011-08-08 19:37 ` [PATCH 4/9] faq/doc: ubi(fs): move "bug report" questions to FAQ Brian Norris
2011-08-08 19:37 ` [PATCH 5/9] doc: nand: update YAFFS URL Brian Norris
2011-08-08 19:37 ` [PATCH 6/9] doc: update info on compiling mtd-utils Brian Norris
2011-08-08 19:37 ` [PATCH 7/9] faq: ubi(fs): sending bug reports using `mtdinfo' Brian Norris
2011-08-09 22:03   ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 8/9] faq: ubi(fs): small spelling, URL fixups Brian Norris
2011-08-09 22:05   ` [PATCH v2 " Brian Norris
2011-08-08 19:37 ` [PATCH 9/9] faq: general: add bug reporting FAQ Brian Norris
2011-08-09  8:10   ` Brian Foster
2011-08-09 22:05   ` [PATCH v2 " Brian Norris
2011-08-10  7:54     ` Brian Foster [this message]
2011-08-10  8:34       ` [PATCH " Brian Norris
2011-08-08 20:00 ` [PATCH 0/9] mtd-www: various fixes, bug reporting info Artem Bityutskiy
2011-08-15 12:19 ` Artem Bityutskiy

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=201108100954.11266.brian.foster@maxim-ic.com \
    --to=brian.foster@maxim-ic.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox