Hi,
> Justin, Erik is right. You should try to be more careful.
I do try to be careful but I made a mistake. I have no issue with constructive
criticism. My response was trying to inject a little humour into the situation
and perhaps point out we're being IMO a little silly about this. There sh
One of the phrases I try to practice is this [1]. It gives the assumption
that the text doesn't convey jokes and sarcasm well.
[1] "Assume positive intent".
-Mark
>
> Erik, I’m not sure Justin takes criticism very well from you. It might be
> more effective if you leave that to someone else.
>
I'm afraid you're right :-(
Thanks for taking this one. I'll refrain from commenting any more on this
or future instances (of which I hope there will be few).
EdB
Justin, Erik is right. You should try to be more careful. I’m a native English
speaker and I had to read it more than once to make sure I read it right. I was
not sure if you were referring to a specific tag. There’s no reason to get
defensive. Take it for what it was: constructive criticism.
E
Hi,
> "what what teh"?
I don't think we need remind people every time they get a a letter out of place
or autocorrect picks the wrong word. Not matter how careful you are mistakes
are sill going to slip though.
Also:
Aoccdrnig to rscheearch at Cmabrigde Uinervtisy, it deosn't mttaer in waht
o
>
> Shouldn't this point what what teh tag will be when the software is
> released?
>
"what what teh"?
Please be more careful writing emails, as per our recent consensus on email
etiquette. Mistakes in spelling easily translate into misunderstandings
about intend. There is no hurry when dealing w
Hi,
Just had a look at RC3 and looks like with still have the pom tag issue;
apache-flex-tool-api-1.0.0-RC3
Shouldn't this point what what teh tag will be when the software is released?
Justin
I ran rat, it didn't catch anything but the DEPENDENCIES, for which I added
an exception. Are these files platform specific?
And the 'nits', you can basically do what you think is best, but at the
risk of starting another huge thread about nothing: either en_US or en_GB
are perfectly fine for the
Ugh, somehow we all missed the fact that there aren’t Apache headers on
assembly/assemble*.xml. Can anyone think of a way we can make an
exception? Are they auto-generated? Did they come from somewhere else?
Do the lack any creativity? Otherwise we have to roll an RC3. I checked
in Apache head
