Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Nicolas Bonifas <nicolas.bonifas@free.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: gcore man page
Date: Mon, 22 Oct 2007 23:36:00 -0000	[thread overview]
Message-ID: <1193092681.13911.7.camel@localhost.localdomain> (raw)
In-Reply-To: <471D0F93.8020008@free.fr>

On Mon, 2007-10-22 at 23:01 +0200, Nicolas Bonifas wrote:
> gcore had no man page, here is one!
> Regards,
> Nicolas

Thanks.  This looks like a good start, but raises a lot of questions.
For instance:

 * Is this meant to be about the gcore facility provided by gdb?
If not, of course, this is the wrong mailing list.

Assuming yes, then:

 * The copyright date can't be any earlier than 2003, which is 
when that feature was introduced.  I might suggest:

   Copyright (C) 2003, 2005, 2007 Free Software Foundation, Inc.

since that's what it says in the shell script.

 * Where, and when (under what circumstances) should this man
page get installed?  We do have a shell script, gdb_gcore.sh, 
that invokes gdb from the shell and performs the "gcore" function,
but none of our makefiles ever install this shell script.

If we do install the shell script, we probably want to rename it
to "gcore" (or else the man page should mention the alternate 
name).

I'm happy to have these issues discussed and/or resolved...

Michael



  reply	other threads:[~2007-10-22 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 21:09 Nicolas Bonifas
2007-10-22 23:36 ` Michael Snyder [this message]
2007-10-24 19:12   ` Nicolas Bonifas
2007-10-24 22:06     ` Michael Snyder

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=1193092681.13911.7.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nicolas.bonifas@free.fr \
    /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