3:14 AM
Subject: Re: ban on code formatting when release branch is active
I was thinking partly of Javadoc, also when source files are packaged up
in
jars etc. It can be useful to know which version of a source file is
present
(e.g. if one knows that a bug was fixed in version x); without
Ugh, I hereby ban any use of auto code formatting tools when there's an
active release branch that I have to merge into main.
I also ban cvs header tags inside of files. We don't use them and they
also make merges tedious.
--
Michael Stover [EMAIL PROTECTED]
Apache Software Foundation
, and thus make the merge job easier.
Do you use Eclipse for difference checking?
S.
- Original Message -
From: Michael Stover [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 20, 2004 2:13 AM
Subject: ban on code formatting when release branch is active
Ugh, I hereby ban any
Eclipse for difference checking?
S.
- Original Message -
From: Michael Stover [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, June 20, 2004 2:13 AM
Subject: ban on code formatting when release branch is active
Ugh, I hereby ban any use of auto code formatting tools when
investigation tomorrow - surely there must be a
solution to this.
Sebastian
- Original Message -
From: Michael Stover [EMAIL PROTECTED]
To: JMeter Developers List [EMAIL PROTECTED]
Sent: Sunday, June 20, 2004 2:30 AM
Subject: Re: ban on code formatting when release branch is active
Yes, $Header
Absolutely agree.
Just before code freeze prior to each release, maybe?
--
Salut,
Jordi.
[EMAIL PROTECTED] wrote:
Not that I want to extend a discussion on code formatting standards
longer than I have to, but...
It might be best to disallow code formatting via programmatic
means (ie, hitting
Hello,
It looks like people were generally in favor of bumping up the 80
column width limit, but we didn't really make a decision. It can be
rather difficult to come to an agreement when we are dealing with a
sliding scale (80 columns? 100? 120? Personally I prefer 117.5.) So
let's
Jordi Salvat i Alabart: -0
...because the nice thing about standards is that if you don't like any
of the ones out there you can always create your own... (the sentence is
not mine, but I can't remember the author, sorry Mr/Ms. author).
--
Salut,
Jordi.
Jeremy Arnold wrote:
Hello,
It looks
Not that I want to extend a discussion on code formatting standards
longer than I have to, but...
It might be best to disallow code formatting via programmatic
means (ie, hitting ctrl-shift-F in Eclipse or using pretty printers).
The reason is that no matter what standards you decide
, Jeremy Arnold wrote:
Hello,
Back in January, the JMeter committers agreed to use the
Jakarta-Turbine conventions for code formatting
(http://jakarta.apache.org/turbine/common/code-standards.html). Not my
personal favorite, but I'm not picky as long as there is some kind of
convention
vertical and horizontal
space.
What do people say? Who out there needs an 80 column max? Can people go to 120 or
higher?
-Mike
On 16 Aug 2003 at 20:39, Jeremy Arnold wrote:
Hello,
Back in January, the JMeter committers agreed to use the
Jakarta-Turbine conventions for code formatting
11 matches
Mail list logo
