+1
Rana Dasgupta wrote:
+1
And the JIRA has logging properties as well. On several threads now, email
patches have just caused more confusion, with participants asking if these
are examples or live code.
On 10/4/06, Mikhail Fursov [EMAIL PROTECTED] wrote:
I do not like JIRA too,
On 10/4/06, Salikh Zakirov [EMAIL PROTECTED] wrote:
Salikh Zakirov wrote:
The patch turned out to be exact duplicate of HARMONY-1571.
Besides, there exist a patch with fixes for unit tests: HARMONY-1574.
The following change is needed on top of already committed HARMONY-1551
to make DRLVM
On 5 October 2006 at 13:57, Ivan Volosyuk [EMAIL PROTECTED] wrote:
On 10/4/06, Salikh Zakirov [EMAIL PROTECTED] wrote:
Salikh Zakirov wrote:
The patch turned out to be exact duplicate of HARMONY-1571.
Besides, there exist a patch with fixes for unit tests: HARMONY-1574.
The
Mark, if you don't care, I'm happy to do it as I'm running through DRLVM
JIRA chains now. Let me know by simply un- or re-assigning
geir
Mark Hindess wrote:
On 5 October 2006 at 13:57, Ivan Volosyuk [EMAIL PROTECTED] wrote:
On 10/4/06, Salikh Zakirov [EMAIL PROTECTED] wrote:
Salikh
The patch turned out to be exact duplicate of HARMONY-1571.
Besides, there exist a patch with fixes for unit tests: HARMONY-1574.
The following change is needed on top of already committed HARMONY-1551
to make DRLVM start on Linux/x86_64.
However, it still doesn't work properly, failing with
Can you open a JIRA with this, explaining what needs to be done, and
linking the other JIRAs as needed?
Thx
geir
Salikh Zakirov wrote:
The patch turned out to be exact duplicate of HARMONY-1571.
Besides, there exist a patch with fixes for unit tests: HARMONY-1574.
The following change is
Okay, I will file a JIRA as soon as I have a complete solution.
A side question: do we have a philosophical justification
why we as a project prefer to work through JIRA instead of e-mail?
I personally believe that the instruction will not get any clearer
if it is written in JIRA rather than in
Salikh Zakirov wrote:
Okay, I will file a JIRA as soon as I have a complete solution.
A side question: do we have a philosophical justification
why we as a project prefer to work through JIRA instead of e-mail?
I personally believe that the instruction will not get any clearer
if it is
I do not like JIRA too, but sending patches by email is even worse:
1) There are a lot of opened JIRA issues. How to track them all by email?
2) New people have no access to the old email threads
3) Patches sometimes are too big to be sent by email.
On 10/4/06, Salikh Zakirov [EMAIL PROTECTED]
Mikhail Fursov wrote:
I do not like JIRA too, but sending patches by email is even worse:
1) There are a lot of opened JIRA issues. How to track them all by email?
Tracking can be done by replying to messages.
And if nobody cares about the patch, JIRA will not help -- patches in JIRA
rot with
Done. HARMONY-1698.
Mark, it looks like you already started looking into it,
that's *real* quick. Thanks a lot!
Geir Magnusson Jr. wrote:
Can you open a JIRA with this, explaining what needs to be done, and
linking the other JIRAs as needed?
Salikh Zakirov wrote:
The patch turned out to be
+1
And the JIRA has logging properties as well. On several threads now, email
patches have just caused more confusion, with participants asking if these
are examples or live code.
On 10/4/06, Mikhail Fursov [EMAIL PROTECTED] wrote:
I do not like JIRA too, but sending patches by email is
12 matches
Mail list logo
