Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@redhat.com
Cc: pgilliam@us.ibm.com, gdb-patches@sources.redhat.com
Subject: Re: fix "too much information" bug w/ "info vector" on PowerPC
Date: Tue, 30 Aug 2005 23:36:00 -0000	[thread overview]
Message-ID: <200508302246.j7UMkfwX015591@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <m3ll2j12v8.fsf@alligator.red-bean.com> (message from Jim Blandy on Tue, 30 Aug 2005 15:22:51 -0700)

> From: Jim Blandy <jimb@redhat.com>
> Date: Tue, 30 Aug 2005 15:22:51 -0700
> 
> Daniel Jacobowitz <drow@false.org> writes:
> > On Tue, Aug 30, 2005 at 02:42:31PM -0700, Jim Blandy wrote:
> >> - I'm not sure why the indentation in your patch is weird, but in any
> >>   case, there seems to be a preference for using spaces in new code,
> >>   not tabs.
> >
> > Er, really?  GNU convention is tabs, as far as I know.
> 
> I don't see anything in the coding standards, but maybe I've missed
> something.

Well, emacs generates tabs by default.

Mark


  parent reply	other threads:[~2005-08-30 22:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 21:44 Paul Gilliam
2005-08-30 21:46 ` Jim Blandy
2005-08-30 22:24   ` Daniel Jacobowitz
2005-08-30 22:30     ` Jim Blandy
2005-08-30 22:44       ` Daniel Jacobowitz
2005-08-30 23:50         ` Jim Blandy
2005-08-30 22:46       ` Stan Shebs
2005-08-30 23:36       ` Mark Kettenis [this message]
2005-08-31  7:52         ` Jim Blandy
2005-08-31 20:30   ` Paul Gilliam
2005-08-31 20:48     ` Jim Blandy
2005-08-31 20:48     ` Daniel Jacobowitz
2005-09-01  0:30       ` Paul Gilliam
2005-09-01 23:07         ` Jim Blandy
2005-09-02  0:55           ` Daniel Jacobowitz
2005-09-02 14:26             ` Paul Gilliam
2005-09-06 18:14             ` Jim Blandy
2005-09-06 18:21               ` Daniel Jacobowitz
2005-09-01 18:12       ` [commit] " Paul Gilliam
2005-08-31 20:26 ` Kevin Buettner
2005-08-31 20:32   ` Paul Gilliam

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=200508302246.j7UMkfwX015591@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=pgilliam@us.ibm.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