From: Eli Zaretskii <eliz@elta.co.il>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Cleanup i386-nat.c
Date: Thu, 04 Mar 2004 06:11:00 -0000 [thread overview]
Message-ID: <uishl9m4c.fsf@elta.co.il> (raw)
In-Reply-To: <200403032030.i23KUvW5001303@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Wed, 3 Mar 2004 21:30:57 +0100 (CET))
> Date: Wed, 3 Mar 2004 21:30:57 +0100 (CET)
> From: Mark Kettenis <kettenis@chello.nl>
>
> I get the felling I somehow stepped on your toes. I'm sorry for that.
> Although there were some genuine style "problems", my main motivation
> for changing the coding style was the fact that it was mere
> inconsistent with the rest of the i386-specific files in GDB. Since
> I, as the i386 target maintainer feel somehow repsonsible for this
> file, I tried to resolve the inconsistencies. In no way do I blame
> you for those inconsistencies.
Well, no offense, but it surely feels like nitpicking that got out of
proportions. I labored on that code not only to make it right, but
also so that it looks good. Most of those ``style problems'' are
really conscious decisions on my part, meant to make the code
aesthetically pleasant.
I understand that our styles may well be different a bit, but since
GDB is a program maintained by lots of people, it is no surprise that
the code style isn't uniform. I don't see anything wrong with that,
provided that the basic GNU coding conventions are preserved. E.g., I
don't see any need to insist on a specific value of comment-column, or
refill comment blocks, unless they are badly malformed. Do we really
need this kind of ``style police''?
I guess bottom line is, I think that minor style differences shouldn't
be a reason for such extensive changes, especially when an area
maintainer intends to exercise his/her privilege of committing such
changes in someone else's code without any discussion.
Am I the only one who thinks so?
WARNING: multiple messages have this Message-ID
From: Eli Zaretskii <eliz@elta.co.il>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Cleanup i386-nat.c
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <uishl9m4c.fsf@elta.co.il> (raw)
Message-ID: <20040319000900.bpc4PCwfXZ_ettrer2Mw9SZa0cpishNb4FRumRgH5Yw@z> (raw)
In-Reply-To: <200403032030.i23KUvW5001303@elgar.kettenis.dyndns.org> (message from Mark Kettenis on Wed, 3 Mar 2004 21:30:57 +0100 (CET))
> Date: Wed, 3 Mar 2004 21:30:57 +0100 (CET)
> From: Mark Kettenis <kettenis@chello.nl>
>
> I get the felling I somehow stepped on your toes. I'm sorry for that.
> Although there were some genuine style "problems", my main motivation
> for changing the coding style was the fact that it was mere
> inconsistent with the rest of the i386-specific files in GDB. Since
> I, as the i386 target maintainer feel somehow repsonsible for this
> file, I tried to resolve the inconsistencies. In no way do I blame
> you for those inconsistencies.
Well, no offense, but it surely feels like nitpicking that got out of
proportions. I labored on that code not only to make it right, but
also so that it looks good. Most of those ``style problems'' are
really conscious decisions on my part, meant to make the code
aesthetically pleasant.
I understand that our styles may well be different a bit, but since
GDB is a program maintained by lots of people, it is no surprise that
the code style isn't uniform. I don't see anything wrong with that,
provided that the basic GNU coding conventions are preserved. E.g., I
don't see any need to insist on a specific value of comment-column, or
refill comment blocks, unless they are badly malformed. Do we really
need this kind of ``style police''?
I guess bottom line is, I think that minor style differences shouldn't
be a reason for such extensive changes, especially when an area
maintainer intends to exercise his/her privilege of committing such
changes in someone else's code without any discussion.
Am I the only one who thinks so?
next prev parent reply other threads:[~2004-03-04 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 15:38 Mark Kettenis
2004-02-29 6:05 ` Eli Zaretskii
2004-02-29 9:41 ` Mark Kettenis
2004-02-29 18:48 ` Eli Zaretskii
2004-03-19 0:09 ` Mark Kettenis
2004-03-03 20:31 ` Mark Kettenis
2004-03-04 6:11 ` Eli Zaretskii [this message]
2004-03-19 0:09 ` Eli Zaretskii
2004-03-03 6:11 ` Eli Zaretskii
2004-03-19 0:09 ` 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=uishl9m4c.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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