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:21:00 -0000 [thread overview]
Message-ID: <20120329062107.22774.qmail@sourceware.org> (raw)
The branch, archer-jankratochvil-autoload has been updated
via c1432dc38024d31f9d516fe5cb82e626d545c4d7 (commit)
via f689bc8eebae7ac31c75c2bbf12e5a2d8303dcac (commit)
via 8c91fda42db4201841a3efa95c75e980313ce44b (commit)
via 3ab11dbf18b0662fe177fc190abaa17c9f3ddb31 (commit)
via 88b620700aee30203eb47d72799a84cf050701b2 (commit)
from 19a857b39dd91f576d034d9a7e4d71b8e32604f8 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email.
- Log -----------------------------------------------------------------
commit c1432dc38024d31f9d516fe5cb82e626d545c4d7
Merge: 19a857b f689bc8
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:20:58 2012 +0200
Merge branch 'secmove-misc2-warn-safepath-debug' into secmove-misc2-warn-safepath-debug-warnlocal
commit f689bc8eebae7ac31c75c2bbf12e5a2d8303dcac
Merge: a727a31 8c91fda
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:20:58 2012 +0200
Merge branch 'secmove-misc2-warn-safepath' into secmove-misc2-warn-safepath-debug
commit 8c91fda42db4201841a3efa95c75e980313ce44b
Merge: 54fbd69 3ab11db
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:20:57 2012 +0200
Merge branch 'secmove-misc2-warn' into secmove-misc2-warn-safepath
commit 3ab11dbf18b0662fe177fc190abaa17c9f3ddb31
Merge: 8bb9979 88b6207
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:20:57 2012 +0200
Merge branch 'secmove-misc2' into secmove-misc2-warn
commit 88b620700aee30203eb47d72799a84cf050701b2
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date: Thu Mar 29 08:20:54 2012 +0200
.
-----------------------------------------------------------------------
Summary of changes:
gdb/doc/gdb.texinfo | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
First 500 lines of diff:
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index ee97085..70e27cd 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -20883,7 +20883,8 @@ current directory have been auto-loaded.
canned sequences of commands (@pxref{Sequences}), as long as @samp{set
auto-load gdb-scripts} is set to @samp{yes}.
-Please refer to @ref{objfile-gdb.py file} description as it is similar.
+For more background refer to the similar Python scripts auto-loading
+description (@pxref{objfile-gdb.py file}).
@table @code
@anchor{set auto-load gdb-scripts}
hooks/post-receive
--
Repository for Project Archer.
next reply other threads:[~2012-03-29 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 6:21 jkratoch [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-29 8:50 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=20120329062107.22774.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).