Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: document GDB's overlay support
Date: Sun, 25 Nov 2001 08:33:00 -0000	[thread overview]
Message-ID: <np667rdg3b.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: "Eli Zaretskii"'s message of Fri, 30 Nov 2001 23:57:21 +0200


"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > *** gdb/doc/gdb.texinfo	2001/09/12 19:49:52	1.51
> > --- gdb/doc/gdb.texinfo	2001/10/09 16:40:00
> 
> This patch is approved, with the following minor comments:

Great, I'll assume this approval applies (with the comments) to my
text-only patch as well.


> > + *** makeinfo/makeinfo.c.~1~	Sun Sep 19 10:24:44 1999
> > + --- makeinfo/makeinfo.c	Wed Sep 26 10:49:48 2001
> 
> Did you send this to the Texinfo maintainer?

Yes.

> If so, is this patch available in Texinfo 4.0d, the latest pretest
> on alpha.gnu?

I don't know.

> In any case, if the only problem is that makeinfo doesn't search the
> include directories for images, people could force it to DTRT by
> simlpy putting the image files in the current directory, right?
> Perhaps it's better to tell them to do this, instead of rebuilding
> makeinfo?

That would be simpler.

I guess I wanted to provide instructions for putting your build system
back in a "working normal" state: you type "cvs update", "configure",
and "make", and things just work, without needing to remember to copy
over certain files.

But obviously, the instructions should mention the simpler
alternative, for those less forgetful than me.


WARNING: multiple messages have this Message-ID
From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: document GDB's overlay support
Date: Fri, 30 Nov 2001 14:53:00 -0000	[thread overview]
Message-ID: <np667rdg3b.fsf@zwingli.cygnus.com> (raw)
Message-ID: <20011130145300.r60zXsF5_UuKFOj9Wv72R8xo1MCOWKW4cOpIpQxyo4A@z> (raw)
In-Reply-To: <8582-Fri30Nov2001235720+0200-eliz@is.elta.co.il>

"Eli Zaretskii" <eliz@is.elta.co.il> writes:
> > *** gdb/doc/gdb.texinfo	2001/09/12 19:49:52	1.51
> > --- gdb/doc/gdb.texinfo	2001/10/09 16:40:00
> 
> This patch is approved, with the following minor comments:

Great, I'll assume this approval applies (with the comments) to my
text-only patch as well.


> > + *** makeinfo/makeinfo.c.~1~	Sun Sep 19 10:24:44 1999
> > + --- makeinfo/makeinfo.c	Wed Sep 26 10:49:48 2001
> 
> Did you send this to the Texinfo maintainer?

Yes.

> If so, is this patch available in Texinfo 4.0d, the latest pretest
> on alpha.gnu?

I don't know.

> In any case, if the only problem is that makeinfo doesn't search the
> include directories for images, people could force it to DTRT by
> simlpy putting the image files in the current directory, right?
> Perhaps it's better to tell them to do this, instead of rebuilding
> makeinfo?

That would be simpler.

I guess I wanted to provide instructions for putting your build system
back in a "working normal" state: you type "cvs update", "configure",
and "make", and things just work, without needing to remember to copy
over certain files.

But obviously, the instructions should mention the simpler
alternative, for those less forgetful than me.


  reply	other threads:[~2001-11-30 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-23 15:06 Jim Blandy
2001-11-25  1:01 ` Eli Zaretskii
2001-11-25  8:33   ` Jim Blandy [this message]
2001-11-25 10:57     ` Eli Zaretskii
2001-11-30 22:53       ` Eli Zaretskii
2001-11-30 14:53     ` Jim Blandy
2001-12-02 21:57     ` Andrew Cagney
2001-11-30 13:58   ` Eli Zaretskii
2001-11-30 12:57 ` Jim Blandy

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=np667rdg3b.fsf@zwingli.cygnus.com \
    --to=jimb@zwingli.cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    /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