From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] package/at: updated version from 3.1.13 to 3.1.16
Date: Mon, 7 Sep 2015 11:46:01 +0100 [thread overview]
Message-ID: <55ED6AE9.9070805@imgtec.com> (raw)
In-Reply-To: <55ED6A8E.6010003@imgtec.com>
> Also, when you send a new patch with superseded an old one, please mark
s/with superseded/that supersedes/
next prev parent reply other threads:[~2015-09-07 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 8:30 [Buildroot] [PATCH 1/5] package/at: updated version from 3.1.13 to 3.1.16 Francesco Nwokeka
2015-09-07 10:44 ` Vicente Olivert Riera
2015-09-07 10:46 ` Vicente Olivert Riera [this message]
2015-09-07 11:55 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2015-09-04 17:49 Francesco Nwokeka
2015-09-04 17:45 Francesco Nwokeka
2015-09-04 17:44 Francesco Nwokeka
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=55ED6AE9.9070805@imgtec.com \
--to=vincent.riera@imgtec.com \
--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.