Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Wiki: Started a page on how to write testcases for GDB
Date: Sat, 26 Dec 2009 09:06:00 -0000	[thread overview]
Message-ID: <838wcq5ch8.fsf@gnu.org> (raw)
In-Reply-To: <20091226085656.GY24363@adacore.com>

> Date: Sat, 26 Dec 2009 12:56:56 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb@sourceware.org
> 
> > Thanks.
> > It would be nice to have this as part of gdbint.texinfo as well.
> 
> I think we should put the info in either document, but not both, or
> we would be duplicating the info.  I chose the Wiki because it's very
> easy to update and maintain.  To be honest, I don't think I will have
> the courage to make fixes if it means having to go through the normal
> review process.

You don't need to add this to gdbint.texinfo until it's in good shape
and sufficiently complete.  Likewise, not every change on the wiki
needs to be immediately reflected in the manual, you can do that only
after a substantial amount of changes went in.  OTOH, fixing a typo or
some similar trivial correction don't need to be reviewed, and if they
are, the result is known in advance.

IOW, I'm willing to make a lot of allowances if that will convince you ;-)

My rationale is very simple: if we start putting important parts of
documentation on the wiki, then why maintain the manuals at all?


  reply	other threads:[~2009-12-26  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26  5:45 Joel Brobecker
2009-12-26  5:56 ` Joel Brobecker
2009-12-26  8:44 ` Eli Zaretskii
2009-12-26  8:57   ` Joel Brobecker
2009-12-26  9:06     ` Eli Zaretskii [this message]
2009-12-27  0:59       ` Christopher Faylor

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=838wcq5ch8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@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