Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Bob Wilson <bwilson@tensilica.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] print newline after copyright message
Date: Thu, 27 Jul 2006 21:33:00 -0000	[thread overview]
Message-ID: <20060727213258.GC28145@nevyn.them.org> (raw)
In-Reply-To: <44C530F7.8090306@tensilica.com>

On Mon, Jul 24, 2006 at 01:43:35PM -0700, Bob Wilson wrote:
> I don't work on GDB much, so I'm not on the write-after-approval list in 
> the MAINTAINERS file.  If my write access for binutils applies to the gdb 
> directory (I don't know how that works), I would be happy to apply the 
> patch.  Is that OK? Otherwise, would you apply it for me?  Here is the 
>  revised changelog:

You aren't actually in the right group, so I've applied the patch.  If
you'd like write access to GDB, though, let me know.

My eye is actually somewhat confused by the new layout, since I was so
used to the old:

drow@caradoc:/space/fsf/x86-64/commit-gdb/gdb% ./gdb =gdb
GNU gdb 6.5.50.20060727-cvs
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
Setting up the environment for debugging gdb.

But I think it's still better.  If someone else wants to rearrange the
newlines again later, I'll let them :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-07-27 21:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 20:35 Bob Wilson
2006-07-24 20:18 ` Daniel Jacobowitz
2006-07-24 20:43   ` Bob Wilson
2006-07-27 21:33     ` Daniel Jacobowitz [this message]
2006-07-27 23:06       ` Bob Wilson

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=20060727213258.GC28145@nevyn.them.org \
    --to=drow@false.org \
    --cc=bwilson@tensilica.com \
    --cc=gdb-patches@sources.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