All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 04/11] working-with: board support
Date: Tue, 26 Feb 2013 18:45:11 +0100	[thread overview]
Message-ID: <512CF4A7.1030802@mind.be> (raw)
In-Reply-To: <bd4236ff40f9132d14f2f6610588847e92df93dc.1361827174.git.s.martin49@gmail.com>

On 25/02/13 22:31, Samuel Martin wrote:
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
>
> ---
> Changes since v1:
> * simplify cross-ref (Arnout)
> ---
>   docs/manual/working-with.txt | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/docs/manual/working-with.txt b/docs/manual/working-with.txt
> index a57169c..4432b54 100644
> --- a/docs/manual/working-with.txt
> +++ b/docs/manual/working-with.txt
> @@ -25,5 +25,5 @@ interested in hacking it to add:
>
>   * new packages: refer to the xref:adding-packages[Developer guide]
>
> -* new board support: refer to the xref:customize-store[], more specifically
> -  xref:customize-store-board-support[].
> +* new board support: refer to the
> +  xref:customize-store-board-support[Developer guide].
>

  Could you merge this with patch 1/11 (adding your own SoB of course)?

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-02-26 17:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 21:31 [Buildroot] [pull request v2] Pull request for branch for-master/doc Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 01/11] manual: fix cross-refs Samuel Martin
2013-02-28 21:38   ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 02/11] manual: minor fix in patch-policy.txt Samuel Martin
2013-02-26  8:29   ` Thomas Petazzoni
2013-02-26  9:44     ` Samuel Martin
2013-02-26 11:01       ` Thomas Petazzoni
2013-02-26 11:15         ` Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 03/11] manual: misc. post-{build, image} scripts fixes Samuel Martin
2013-02-26  8:30   ` Thomas Petazzoni
2013-02-28 21:39   ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 04/11] working-with: board support Samuel Martin
2013-02-26 17:45   ` Arnout Vandecappelle [this message]
2013-02-28 21:39   ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 05/11] support: add kconfiglib python module Samuel Martin
2013-02-26 20:18   ` Arnout Vandecappelle
2013-02-25 21:31 ` [Buildroot] [PATCH 06/11] support/scripts: add gen-manual-lists.py Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 07/11] manual: add a make target 'manual-update-lists' Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 08/11] manual: cleanup appendix.txt Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 09/11] Makefile: add to the release target a warning about the manual updates Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 10/11] manual: update generated lists Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 11/11] Manual: add empty line after header in .mk files Samuel Martin
2013-02-28 21:39   ` Peter Korsgaard

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=512CF4A7.1030802@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.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 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.