Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: nathan@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: more missing gplv3 notices
Date: Tue, 17 Mar 2009 20:03:00 -0000	[thread overview]
Message-ID: <uk56oq6nl.fsf@gnu.org> (raw)
In-Reply-To: <20090317191251.GA24913@caradoc.them.org>

> Date: Tue, 17 Mar 2009 15:12:51 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Nathan Sidwell <nathan@codesourcery.com>, gdb-patches@sourceware.org
> 
> >    2009-01-12  Christopher Faylor  <me+cygwin@cgf.cx>
> > 
> > 	   * amd64-windows-nat.c Rename gdb-specific win32_* to windows_*
> > 	   throughout.
> > 	   * i386-cygwin-tdep.c: Ditto.
> > 	   * i386-windows-nat.c: Ditto.
> > 	   * windows-nat.h: Ditto.
> > 	   * windows-tdep.c: Ditto.
> > 	   * windows-tdep.h: Ditto.
> > 	   * windows-nat.c: Ditto.
> > 
> > See the node "Style of Change Logs" in standards.info for details.
> 
> It does not say that explicitly (doesn't mention multi-file changes at
> all), and this is not the prevailing style used by GDB developers
> based on my survey of the changelogs.

Sorry, I forgot I shouldn't talk about these things.


  reply	other threads:[~2009-03-17 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16  9:49 Nathan Sidwell
2009-03-16 19:32 ` Eli Zaretskii
2009-03-17 11:36   ` Nathan Sidwell
2009-03-17 19:04     ` Eli Zaretskii
2009-03-17 19:28       ` Daniel Jacobowitz
2009-03-17 20:03         ` Eli Zaretskii [this message]
2009-03-18 16:01           ` Alfred M. Szmidt
2009-03-18 16:12             ` Pedro Alves
2009-03-18 16:33               ` Alfred M. Szmidt
2009-03-18 19:24                 ` Pedro Alves
2009-03-18 11:05       ` Nathan Sidwell

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=uk56oq6nl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nathan@codesourcery.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