Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: suggestion for future changes to GDB website
Date: Wed, 26 Oct 2005 06:45:00 -0000	[thread overview]
Message-ID: <20051026002923.GC1155@adacore.com> (raw)
In-Reply-To: <vt2fyqpw2es.fsf@theseus.home.>

> Joel Brobecker <brobecker@adacore.com> writes:
> > I would like to suggest that we post changes to the htdocs CVS repository
> > to this mailing-list. That way, all developers have a chance to see and
> > react to changes. This does not necessarily mean that we should go
> > through the same formal process, with changelogs and all, but it would
> > be nice to see the patches, with a short explaination containing the
> > reason for the change if necessary.
> 
> Do you mean posting the changes before they're committed, or after?

I'm thinking after, but it's not a strong opinion.

> If after, why not just set up an automatic patches list, as used for
> the source code?

That's an option. The nice thing about posting the patch here is that
you can add an explaination to the patch. Revision histories are
sometimes a bit obscure...

-- 
Joel


  parent reply	other threads:[~2005-10-26  0:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-26  0:29 Joel Brobecker
     [not found] ` <vt2fyqpw2es.fsf@theseus.home.>
2005-10-26  6:45   ` Joel Brobecker [this message]
2005-10-26 19:36     ` Daniel Jacobowitz
     [not found]     ` <vt2ek67vlew.fsf@theseus.home.>
2005-10-28 18:10       ` Joel Brobecker
2005-10-28 18:16         ` Daniel Jacobowitz
2005-10-28 18:20           ` Joel Brobecker
2005-10-29 10:32           ` Eli Zaretskii
2005-10-26 12:55 ` Eli Zaretskii
2005-10-26 12:57   ` Daniel Jacobowitz
2005-10-26 22:29     ` Eli Zaretskii

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=20051026002923.GC1155@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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