public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: jkratoch@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM] archer-jankratochvil-autoload: Merge branch 'secmove-misc2-warn-safepath-debug' into secmove-misc2-warn-safepath-debug-warnlocal
Date: Thu, 29 Mar 2012 06:07:00 -0000 [thread overview]
Message-ID: <20120329060713.18641.qmail@sourceware.org> (raw)
The branch, archer-jankratochvil-autoload has been updated
via 6bdc93591ac355c28cedbf8c0213fafaa179e3ae (commit)
via cc31608164b4b1310619de2cfed1d7149ed6ca73 (commit)
via 61a50032375623a045d216e45fddbb6249e8d2d7 (commit)
via 8bb9979be2be7b86dfbbd5b9cb59699086c65b9a (commit)
via be21e52eb8c71b78e095971999998909ff541c0f (commit)
from 35bc74010587a44dff427583a729ea95d68e8bb2 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email.
- Log -----------------------------------------------------------------
commit 6bdc93591ac355c28cedbf8c0213fafaa179e3ae
Merge: 35bc740 cc31608
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:07:02 2012 +0200
Merge branch 'secmove-misc2-warn-safepath-debug' into secmove-misc2-warn-safepath-debug-warnlocal
commit cc31608164b4b1310619de2cfed1d7149ed6ca73
Merge: bdf2f1a 61a5003
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:07:01 2012 +0200
Merge branch 'secmove-misc2-warn-safepath' into secmove-misc2-warn-safepath-debug
commit 61a50032375623a045d216e45fddbb6249e8d2d7
Merge: 664ca78 8bb9979
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:07:01 2012 +0200
Merge branch 'secmove-misc2-warn' into secmove-misc2-warn-safepath
commit 8bb9979be2be7b86dfbbd5b9cb59699086c65b9a
Merge: fb5d0fd be21e52
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:07:01 2012 +0200
Merge branch 'secmove-misc2' into secmove-misc2-warn
commit be21e52eb8c71b78e095971999998909ff541c0f
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:06:57 2012 +0200
.
-----------------------------------------------------------------------
Summary of changes:
gdb/linux-thread-db.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
First 500 lines of diff:
diff --git a/gdb/linux-thread-db.c b/gdb/linux-thread-db.c
index ee6bdd2..e4341d8 100644
--- a/gdb/linux-thread-db.c
+++ b/gdb/linux-thread-db.c
@@ -78,8 +78,8 @@
static char *libthread_db_search_path;
-/* Whether thread_db auto-loading is enabled by the "set auto-load libthread-db"
- command. */
+/* Set to non-zero if thread_db auto-loading is enabled
+ by the "set auto-load libthread-db" command. */
static int auto_load_thread_db = 1;
/* "show" command for the auto_load_thread_db configuration variable. */
hooks/post-receive
--
Repository for Project Archer.
next reply other threads:[~2012-03-29 6:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 6:07 jkratoch [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-29 8:50 jkratoch
2012-03-29 6:21 jkratoch
2012-03-29 6:17 jkratoch
2012-03-29 5:45 jkratoch
2012-03-28 20:31 jkratoch
2012-03-25 19:10 jkratoch
2012-03-25 19:02 jkratoch
2012-03-25 16:56 jkratoch
2012-03-24 17:25 jkratoch
2012-03-24 9:09 jkratoch
2012-03-20 19:39 jkratoch
2012-03-20 19:38 jkratoch
2012-03-20 0:17 jkratoch
2012-03-19 20:15 jkratoch
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=20120329060713.18641.qmail@sourceware.org \
--to=jkratoch@sourceware.org \
--cc=archer-commits@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).