Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, dje@google.com
Subject: [doc commit] auto-load: Remove trailing @dots  [Re: [patch] auto-load safe-path reset back by set ""]
Date: Mon, 23 Apr 2012 18:13:00 -0000	[thread overview]
Message-ID: <20120423172414.GA29528@host2.jankratochvil.net> (raw)
In-Reply-To: <831unfh68v.fsf@gnu.org>

On Sun, 22 Apr 2012 22:16:32 +0200, Eli Zaretskii wrote:
> > +@item @kbd{gdb -iex "set auto-load safe-path /" [@dots{}]}
> 
> I'd lose the [ and ] part -- you don't need them.

I committed it as obvious but I see you probably meant

@item @kbd{gdb -iex "set auto-load safe-path /" @dots{}}

while I committed

@item @kbd{gdb -iex "set auto-load safe-path /"}

Going to fix it up.


Sorry for double-commit,
Jan


http://sourceware.org/ml/gdb-cvs/2012-04/msg00183.html

--- src/gdb/doc/ChangeLog	2012/04/22 15:49:21	1.1299
+++ src/gdb/doc/ChangeLog	2012/04/23 17:20:56	1.1300
@@ -1,3 +1,8 @@
+2012-04-23  Jan Kratochvil  <jan.kratochvil@redhat.com>
+
+	* gdb.texinfo (Auto-loading safe path): Remove trailing [@dots{}].
+	Three times.
+
 2012-04-22  Jan Kratochvil  <jan.kratochvil@redhat.com>
 
 	* gdb.texinfo (Auto-loading safe path): Replace @itemize @bullet
--- src/gdb/doc/gdb.texinfo	2012/04/22 15:49:21	1.946
+++ src/gdb/doc/gdb.texinfo	2012/04/23 17:20:56	1.947
@@ -21142,11 +21142,11 @@
 You have to specify also any existing directories displayed by
 by @samp{show auto-load safe-path} (such as @samp{/usr:/bin} in this example).
 
-@item @kbd{gdb -iex "set auto-load safe-path /usr:/bin:~/src/gdb" [@dots{}]}
+@item @kbd{gdb -iex "set auto-load safe-path /usr:/bin:~/src/gdb"}
 Specify this directory as in the previous case but just for a single
 @value{GDBN} session.
 
-@item @kbd{gdb -iex "set auto-load safe-path" [@dots{}]}
+@item @kbd{gdb -iex "set auto-load safe-path"}
 Disable auto-loading safety for a single @value{GDBN} session.
 This assumes all the files you debug during this @value{GDBN} session will come
 from trusted sources.
@@ -21161,7 +21161,7 @@
 also suppresses any such warning messages:
 
 @table @asis
-@item @kbd{gdb -iex "set auto-load no" [@dots{}]}
+@item @kbd{gdb -iex "set auto-load no"}
 You can use @value{GDBN} command-line option for a single @value{GDBN} session.
 
 @item @file{~/.gdbinit}: @samp{set auto-load no}


  reply	other threads:[~2012-04-23 18:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 16:52 [patch] auto-load safe-path reset back by set "" Jan Kratochvil
2012-04-22 21:26 ` Eli Zaretskii
2012-04-23 18:13   ` Jan Kratochvil [this message]
2012-04-23 18:02     ` [doc commit#2] auto-load: Remove trailing @dots [Re: [patch] auto-load safe-path reset back by set ""] Jan Kratochvil
2012-04-23 22:52   ` [patch] auto-load safe-path reset back by set "" Jan Kratochvil
2012-04-24  2:53     ` Eli Zaretskii
2012-04-24  3:25       ` Jan Kratochvil
2012-05-06 15:32         ` [commit] " Jan Kratochvil
2012-04-23  2:38 ` Doug Evans
2012-04-23  4:53   ` Jan Kratochvil
2012-04-24  0:58   ` [patch] auto-load safe-path default=$ddir/auto-load [Re: [patch] auto-load safe-path reset back by set ""] Jan Kratochvil
2012-05-06 16:20     ` obsolete: " Jan Kratochvil

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=20120423172414.GA29528@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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