Florian Weimer wrote:
http://www-128.ibm.com/developerworks/java/library/j-jtp09275.html - Yummy.
Soot and JCVM already implement this as well, IIRC. The problems Tim
mentioned are addressed by JCVM by relying on inlining to expose stack
allocation opportunities.
The conclusion reache
[EMAIL PROTECTED] wrote:
BTW, I think it is too early for this to go to a vote. Right now, all
of the binding votes would be cast by people who haven't written any
code on the project. I would favor addressing this issue once there are
some active committers. For now laissez-faire should rul
On Oct 3, 2005, at 3:05 PM, [EMAIL PROTECTED] wrote:
Geir Magnusson Jr. wrote:
I was just discussing it to find out what people thought about
the general subject. I didn't call for a vote.
Right and I was stating that I don't think anyone should.
That said, this is an Apache project
Geir Magnusson Jr. wrote:
I was just discussing it to find out what people thought about the
general subject. I didn't call for a vote.
Right and I was stating that I don't think anyone should.
That said, this is an Apache project in the Incubator, and one of the
objectives is to crea
On Oct 3, 2005, at 2:38 PM, [EMAIL PROTECTED] wrote:
Initially the discussion had a component of author tags. It will
be easy to change the policy of author tags to not than vice
versa. Even easier to allow all to do as they feel initially and
set a uniform policy later when the binding
Initially the discussion had a component of author tags. It will be
easy to change the policy of author tags to not than vice versa. Even
easier to allow all to do as they feel initially and set a uniform
policy later when the binding votes can be cast by a basic quorum of
those whom it will
What? I was talking about having a contributor page *and* an AUTHORS
file, independent of the in-file author tag issue, and quite frankly,
I think we should do it now as people are contributing. If anyone
has a real problem with the httpd-style committers page and tracking
AUTHORS in a fi
BTW, I think it is too early for this to go to a vote. Right now, all
of the binding votes would be cast by people who haven't written any
code on the project. I would favor addressing this issue once there are
some active committers. For now laissez-faire should rule.
-Andy
Geir Magnusson
On Oct 3, 2005, at 11:48 AM, Dan Lydick wrote:
I have looked at the HTTPD contributors page and I like it.
I have also looked at the AUTHORS file in Archie Cobbs' code
and I like it as well.
If I had to choose between the two, I'd choose both.
That was my intention. On the website where i
> [Original Message]
> From: Geir Magnusson Jr. <[EMAIL PROTECTED]>
> To:
> Date: 10/1/05 11:10:55 PM
> Subject: [project policy] Author credit and attribution
>
...snip...
>
> I've worked in projects that did it, and some that didn't. When tags
> were there, I think it gave people a chance
> http://www-128.ibm.com/developerworks/java/library/j-jtp09275.html - Yummy.
Soot and JCVM already implement this as well, IIRC. The problems Tim
mentioned are addressed by JCVM by relying on inlining to expose stack
allocation opportunities.
Leo Simons wrote:
I'm against author tags. I've had too many discussion about it in
the past that I don't want to repeat though, so I won't bother ;)
Same here.
SVN + a detailed credits.txt file is a much better way to deal with this
issue and it scales for years, not just for the little ego
12 matches
Mail list logo
