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 08:50:00 -0000 [thread overview]
Message-ID: <20120329085018.22701.qmail@sourceware.org> (raw)
The branch, archer-jankratochvil-autoload has been updated
via ace34d24e7befc46b62e96936b451d44c23e9fe4 (commit)
via 3d9577f0f9e9bc375a99d0c99a334b4cde8cbfa1 (commit)
via be6511a2d98693ac2fd8b0dd83f596e160103c40 (commit)
via a6763cba77d7e1e894ac08039573b7ae716eec70 (commit)
via d114df287c42068a8954e5e02a9dd7ae7700a9a1 (commit)
from c1432dc38024d31f9d516fe5cb82e626d545c4d7 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email.
- Log -----------------------------------------------------------------
commit ace34d24e7befc46b62e96936b451d44c23e9fe4
Merge: c1432dc 3d9577f
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 10:49:59 2012 +0200
Merge branch 'secmove-misc2-warn-safepath-debug' into secmove-misc2-warn-safepath-debug-warnlocal
commit 3d9577f0f9e9bc375a99d0c99a334b4cde8cbfa1
Merge: f689bc8 be6511a
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 10:49:58 2012 +0200
Merge branch 'secmove-misc2-warn-safepath' into secmove-misc2-warn-safepath-debug
commit be6511a2d98693ac2fd8b0dd83f596e160103c40
Merge: 8c91fda a6763cb
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 10:49:58 2012 +0200
Merge branch 'secmove-misc2-warn' into secmove-misc2-warn-safepath
commit a6763cba77d7e1e894ac08039573b7ae716eec70
Merge: 3ab11db d114df2
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 10:49:58 2012 +0200
Merge branch 'secmove-misc2' into secmove-misc2-warn
commit d114df287c42068a8954e5e02a9dd7ae7700a9a1
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 10:28:39 2012 +0200
.
-----------------------------------------------------------------------
Summary of changes:
gdb/doc/gdb.texinfo | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
First 500 lines of diff:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 70e27cd..1d6274c 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -20851,6 +20851,8 @@ current directory have been auto-loaded.
@node libthread_db.so.1 file
@subsection Automatically loading thread debugging library
+This feature is currently present only on @sc{gnu}/Linux native hosts.
+
@value{GDBN} reads and executes the canned sequences of commands from init file
(if any) in the current working directory,
see @ref{Current Directory Init File during Startup}.
hooks/post-receive
--
Repository for Project Archer.
next reply other threads:[~2012-03-29 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 8:50 jkratoch [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-29 6:21 jkratoch
2012-03-29 6:17 jkratoch
2012-03-29 6:07 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=20120329085018.22701.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).