Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: robert.hoehne@gmx.net
Cc: gdb-patches@cygnus.com
Subject: Re: General question about this list here
Date: Fri, 22 Jan 1999 17:55:00 -0000	[thread overview]
Message-ID: <199901230155.RAA09033@andros.cygnus.com> (raw)
Message-ID: <19990122175500.ZFF3z8YLXNCCK5_H8qMpeu0ddsoWqkJHSJpO647ZWjs@z> (raw)
In-Reply-To: <002f01be4665$63d69100$4ca46d86@robby.dittmannsdorf.de>

   From: Robert Hoehne <robert.hoehne@gmx.net>
   Date: Fri, 22 Jan 1999 22:33:44 -0100

   I have sent now some time ago some patches
   here. How long does it take by default to get a positive or
   negative response or, what should I assume, if
   I get no answer. Should I assume, that the patch
   will be applied if the gdb maintainer will have the
   time to do it or should I assume that the patch will
   not be applied?

I've been encouraging our maintainers to send back an ack and to cc
the list, so that everyone will know what's going on.  In general,
if you don't hear back, you should assume that the patch has not
been applied yet.  In your case, the large patches will need a
copyright assignment, which I'm guessing hasn't happened yet?

   Please do not understand me wrong. I know that
   maintaining such a large package like gdb is not
   a trivial job and that it is very time consuming. I simply
   want to know, if I have still have to wait or not.

We should be more responsive than we have been.  I know that our net
contributors work hard on their code to get it into shape to be added
to GDB, and the least we can do is to look at it and respond.  There's
no good reason why we can't respond within a week of the submission.

   Maybe it might be also good, to place the information
   I might get as answer to my questions here to the
   web-page, where the gdb-patches mailing list is described
   and so others, who might have the same questions will
   find the answer already there.

One of my current projects is to improve our net responsiveness and
interaction, and a new web page will be included, most likely on
sourceware.cygnus.com.

							Stan


  parent reply	other threads:[~1999-01-22 17:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-01  0:00 Robert Hoehne
1999-01-22 14:15 ` Robert Hoehne
1999-04-01  0:00 ` Stan Shebs [this message]
1999-01-22 17:55   ` Stan Shebs
1999-04-01  0:00 Robert Hoehne
1999-01-26 12:21 ` Robert Hoehne

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=199901230155.RAA09033@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=gdb-patches@cygnus.com \
    --cc=robert.hoehne@gmx.net \
    /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