From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 7/9] manual: get-involved.txt: fix event order
Date: Tue, 08 Oct 2013 20:04:13 +0200 [thread overview]
Message-ID: <5254491D.7040407@mind.be> (raw)
In-Reply-To: <CAAXf6LVf5gH72TMNh=pTADHfBs66qrUhhC3HrA9-E--pCHh9TQ@mail.gmail.com>
On 10/08/13 11:31, Thomas De Schampheleire wrote:
> Hi Samuel,
>
> On Sat, Oct 5, 2013 at 9:49 PM, Samuel Martin <s.martin49@gmail.com> wrote:
>> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
>> ---
>> docs/manual/get-involved.txt | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/docs/manual/get-involved.txt b/docs/manual/get-involved.txt
>> index 8515d34..49ab54c 100644
>> --- a/docs/manual/get-involved.txt
>> +++ b/docs/manual/get-involved.txt
>> @@ -84,6 +84,12 @@ Currently, this page is mainly used as a _todo-list_.
>> Events
>> ------
>>
>> +Buildroot Developer Days aside FOSDEM 2012 (February 3, 2012 - Brussels)
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +
>> +* Announcement & agenda thread: http://lists.busybox.net/pipermail/buildroot/2012-January/049340.html[]
>> +* Report: http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html[]
>> +
>> Buildroot Developer Days aside ELC-E 2012 (November 3-4, 2012 - Barcelona)
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> @@ -94,8 +100,4 @@ Buildroot presentation at LSM 2012 (July 12-14, 2012 - Geneva)
>>
>> * Announcement: http://lists.busybox.net/pipermail/buildroot/2012-May/053845.html[]
>>
>> -Buildroot Developer Days aside FOSDEM 2012 (February 3, 2012 - Brussels)
>> -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> -* Announcement & agenda thread: http://lists.busybox.net/pipermail/buildroot/2012-January/049340.html[]
>> -* Report: http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html[]
>> --
>
> What is the meaning of 'aside' here ?
> For me, aside means 'next to' in a spatial context.
> In this case, I think we are rather talking about time, in the sense
> that BDD are before or after the mentioned conference. I'm not sure if
> there exists a word like aside/adjacent that can be used in a time
> context, but otherwise we could use:
>
> ... prior to ...
> ... after ...
I think "alongside" is correct. Any native English speaker who can confirm?
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
next prev parent reply other threads:[~2013-10-08 18:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 19:49 [Buildroot] [pull request] Pull request for branch sma/doc-update Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 1/9] manual: minor update in manual generation Samuel Martin
2013-10-06 9:04 ` Thomas Petazzoni
2013-10-06 11:17 ` Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 2/9] manual: developer-guide.txt: cleanup non-existing source Samuel Martin
2013-10-06 9:04 ` Thomas Petazzoni
2013-10-08 7:51 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 3/9] manual: update dependency list to build the documentation Samuel Martin
2013-10-06 9:05 ` Thomas Petazzoni
2013-10-06 16:25 ` Thomas De Schampheleire
2013-10-06 18:21 ` Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 4/9] manual: add information about buildroot toolchain not being relocable and put some hints to use it Samuel Martin
2013-10-06 9:08 ` Thomas Petazzoni
2013-10-06 14:50 ` Samuel Martin
2013-10-08 9:03 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 5/9] manual: configure: add deprecation warning for Crosstool-NG toolchain backend Samuel Martin
2013-10-05 19:49 ` [Buildroot] [PATCH 6/9] manual: introduction.txt: enhance Buildroot presentation Samuel Martin
2013-10-08 9:18 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 7/9] manual: get-involved.txt: fix event order Samuel Martin
2013-10-08 9:31 ` Thomas De Schampheleire
2013-10-08 18:04 ` Arnout Vandecappelle [this message]
2013-10-08 18:28 ` Ryan Barnett
2013-10-05 19:49 ` [Buildroot] [PATCH 8/9] manual: update get-involved section Samuel Martin
2013-10-08 9:39 ` Thomas De Schampheleire
2013-10-05 19:49 ` [Buildroot] [PATCH 9/9] manual: rework Deploying images chapter Samuel Martin
2013-10-08 20:29 ` Arnout Vandecappelle
2013-10-15 20:27 ` Thomas De Schampheleire
2013-10-16 21:29 ` Arnout Vandecappelle
2013-10-17 8:12 ` Thomas De Schampheleire
2013-10-17 8:18 ` Arnout Vandecappelle
2013-10-17 8:43 ` Samuel Martin
2013-10-17 8:40 ` Samuel Martin
2013-10-17 16:24 ` Arnout Vandecappelle
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=5254491D.7040407@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.