From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: bump to 7.3.1
Date: Sat, 1 Oct 2011 23:24:53 +0200 [thread overview]
Message-ID: <201110012324.54139.arnout@mind.be> (raw)
In-Reply-To: <20110930222606.2ed76af5@skate>
On Friday 30 September 2011 22:26:06, Thomas Petazzoni wrote:
> Yegor,
>
> Can you send a patch with a proper description, so that it can be
> applied with git am ?
>
> By proper description I mean :
>
> * Don't forget that everything before the --- is kept in the commit
> log, so don't put "personal" explanations.
Actually, you can put "personal" explanations after the ---. So the
following would work:
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
On my old build system (openSUSE 10.3) I had problems compiling GDB saying
something like my glibc is too old. So I tried the latest version and could
compile without a problem. See the patch below.
Yegor
---
toolchain/gdb/Config.in | 6 ++++++
1 file changed, 6 insertions(+)
I typically use that for the changelog of single patches.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
next prev parent reply other threads:[~2011-10-01 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 6:49 [Buildroot] [PATCH] gdb: bump to 7.3.1 Yegor Yefremov
2011-09-30 20:26 ` Thomas Petazzoni
2011-10-01 21:24 ` Arnout Vandecappelle [this message]
2011-10-01 22:35 ` Yegor Yefremov
2011-10-05 13:16 ` Peter Korsgaard
2011-10-05 13:31 ` Yegor Yefremov
2011-10-05 14:28 ` Peter Korsgaard
2011-10-05 14:57 ` Thomas Petazzoni
2011-10-05 15:26 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2011-10-04 9:05 yegorslists at googlemail.com
2011-10-05 14:07 ` 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=201110012324.54139.arnout@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.