From: Adam Jocksch <ajocksch@redhat.com>
To: Nurdin Premji <npremji@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>, frysk@sourceware.org
Subject: Re: adopting OpenJDK's coding standard[?]?
Date: Thu, 14 Jun 2007 15:17:00 -0000 [thread overview]
Message-ID: <46714F98.2040901@redhat.com> (raw)
In-Reply-To: <46706866.6000504@redhat.com>
Nurdin Premji wrote:
>
> As for the "tweaking" the only issue I know about is a possible
> inconsistency between editor tab sizes and formatter tab sizes, so
> eclipse users should check both these settings to keep them consistent.
>
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=192511>
Hard tabs would avoid this issue, but I guess they aren't en vogue right
now, are they :)
Adam
next prev parent reply other threads:[~2007-06-14 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 13:12 Andrew Cagney
2007-06-14 9:16 ` Nurdin Premji
2007-06-14 15:17 ` Adam Jocksch [this message]
2007-06-14 11:57 ` Mark Wielaard
2007-06-14 13:59 ` Andrew Cagney
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=46714F98.2040901@redhat.com \
--to=ajocksch@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=npremji@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).