From: Trevor Woerner <twoerner@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: crossgcc@sourceware.org
Subject: [PATCH 0 of 2] documentation update
Date: Wed, 16 Nov 2011 22:46:00 -0000 [thread overview]
Message-ID: <patchbomb.1321483525@codei7.fpelectronics.com> (raw)
In this patch series I have attempted to capture
the details of a recent email exchange in the hopes
others will find it (and find it useful).
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2011-11-16 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 22:46 Trevor Woerner [this message]
2011-11-16 22:46 ` [PATCH 1 of 2] docs: --target versus --host Trevor Woerner
2011-11-16 23:18 ` Yann E. MORIN
2011-11-16 23:24 ` Trevor Woerner
2011-11-17 19:26 ` Thomas Petazzoni
2011-11-17 21:56 ` Trevor Woerner
2011-11-16 22:46 ` [PATCH 2 of 2] docs: Add strategies for assembling root filesystems Trevor Woerner
2011-11-16 23:29 ` Yann E. MORIN
2011-11-17 19:29 ` Thomas Petazzoni
2011-11-17 20:15 ` David Wuertele
2011-11-17 20:32 ` Thomas Petazzoni
2011-11-17 23:05 ` Trevor Woerner
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=patchbomb.1321483525@codei7.fpelectronics.com \
--to=twoerner@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).