public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16152] buggy cygwin detection
Date: Thu, 28 Nov 2013 17:32:00 -0000 [thread overview]
Message-ID: <bug-16152-4717-uRmJeZtTBr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16152-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=16152
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, master has been updated
via 514c0aa6a38dd03b2a6ebf7ec293afa518867403 (commit)
from 8b5e6dc2178814b2506793473347073061310ba7 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=514c0aa6a38dd03b2a6ebf7ec293afa518867403
commit 514c0aa6a38dd03b2a6ebf7ec293afa518867403
Author: Pedro Alves <palves@redhat.com>
Date: Thu Nov 28 17:27:36 2013 +0000
Fix PR 16152's ChangeLog entry.
Mention PR 16152. Fix formatting. Make wording match commit log.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-28 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 9:47 [Bug gdb/16152] New: " sledz@dresearch-fe.de
2013-11-27 21:32 ` [Bug gdb/16152] " tromey at redhat dot com
2013-11-28 17:32 ` cvs-commit at gcc dot gnu.org [this message]
2013-12-13 16:52 ` cvs-commit at gcc dot gnu.org
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=bug-16152-4717-uRmJeZtTBr@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).