Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: binutils@sources.redhat.com, gdb@sources.redhat.com, gcc@gcc.gnu.org
Subject: Documenting partial builds (Was Re: ^c now disallowed?)
Date: Fri, 27 Dec 2002 20:07:00 -0000	[thread overview]
Message-ID: <20021228040534.GA3190@doctormoo> (raw)

DJ said:
>I think a better solution to support is documenting how to do a
>partial configure/build without needing the ctrl-c.  So that you'd
>just say "make all-this all-that" and know that it's doing the right
>minimal set of rules.

Now that I've autoconfiscated the top level, this is my next project.  
(I'll get back to cleaning up the top level, but I'll do this first.)

The big question is, *where* should this be documented?  I can document 
the toplevel Makefile interface quite clearly, but I'm very unsure where 
to put said documentation; should I duplicate it in the docs for each 
package (and if so, where in those docs)?  Put it in some special 
location?  What?

--Nathanael


             reply	other threads:[~2002-12-28  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 20:07 Nathanael Nerode [this message]
2002-12-28  4:11 ` Joseph S. Myers

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=20021228040534.GA3190@doctormoo \
    --to=neroden@twcny.rr.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@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