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
Subject: Re: [commit] [doc patch] gdbserver.1: Document all the options and --multi
Date: Sat, 06 Apr 2013 21:45:00 -0000	[thread overview]
Message-ID: <20130406112443.GA15649@host2.jankratochvil.net> (raw)
In-Reply-To: <838v4wdmyp.fsf@gnu.org>

On Sat, 06 Apr 2013 11:31:42 +0200, Eli Zaretskii wrote:
> It seems to come from this line in gdb.1:
> 
> .TH GDB 1 "2013-04-06" "gdb-" "GNU Development Tools"

True, I have introduced a copy-paste bug.


Thanks,
Jan


gdb/doc/
2013-04-06  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* Makefile.in (POD2MAN1, POD2MAN5): Replace $(VERSION) by ../version.in.

diff --git a/gdb/doc/Makefile.in b/gdb/doc/Makefile.in
index b016740..c3c5130 100644
--- a/gdb/doc/Makefile.in
+++ b/gdb/doc/Makefile.in
@@ -172,9 +172,9 @@ TEXI2POD = perl $(srcdir)/../../etc/texi2pod.pl \
 		$(MAKEINFOFLAGS) $(MAKEINFO_EXTRA_FLAGS)
 
 POD2MAN1 = pod2man --center="GNU Development Tools" \
-		   --release="gdb-$(VERSION)" --section=1
+		   --release="gdb-`sed q $(srcdir)/../version.in`" --section=1
 POD2MAN5 = pod2man --center="GNU Development Tools" \
-		   --release="gdb-$(VERSION)" --section=5
+		   --release="gdb-`sed q $(srcdir)/../version.in`" --section=5
 
 # List of man pages generated from gdb.texi
 MAN1S = gdb.1 gdbserver.1


  reply	other threads:[~2013-04-06 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 19:33 Jan Kratochvil
2013-04-05 20:01 ` Eli Zaretskii
2013-04-06  9:31   ` Jan Kratochvil
2013-04-06 13:56     ` Eli Zaretskii
2013-04-06 15:04       ` Jan Kratochvil
2013-04-06 15:49         ` Eli Zaretskii
2013-04-06 15:52           ` [commit] " Jan Kratochvil
2013-04-06 19:26             ` Eli Zaretskii
2013-04-06 21:45               ` Jan Kratochvil [this message]
2013-04-07  6:21                 ` [commit#2] " 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=20130406112443.GA15649@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.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