[
https://issues.apache.org/jira/browse/TS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Giedymin updated TS-166:
--
Attachment: TS-166-v1-part2-JasonGiedymin.patch
> Two scripts, for building and basic config settings for t
[
https://issues.apache.org/jira/browse/TS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Giedymin reopened TS-166:
---
Supplied patches.
> Two scripts, for building and basic config settings for testing.
> -
[
https://issues.apache.org/jira/browse/TS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Giedymin updated TS-166:
--
Attachment: (was: TS-166-v1-part2-JasonGiedymin.patch)
> Two scripts, for building and basic config set
[
https://issues.apache.org/jira/browse/TS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Giedymin updated TS-199:
--
Attachment: TS-199-v3-JasonGiedymin.patch
Adds status call for ubuntu.
Patch includes all changes in v2.
>
[
https://issues.apache.org/jira/browse/TS-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Giedymin updated TS-166:
--
Attachment: TS-166-v1-part2-JasonGiedymin.patch
TS-166-v1-JasonGiedymin.patch
Updates to th
Remap plugin chaining is broken and needs cleanup
-
Key: TS-224
URL: https://issues.apache.org/jira/browse/TS-224
Project: Traffic Server
Issue Type: Bug
Reporter: Leif Hedstrom
[
https://issues.apache.org/jira/browse/TS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom reassigned TS-224:
Assignee: Leif Hedstrom
> Remap plugin chaining is broken and needs cleanup
> -
On 02/26/2010 06:09 PM, John Plevyak wrote:
My vote is #2.
I would like to see a REVIEWERS file, and a general statement
that if you are going to make big changes you should discuss
it on -dev/IRC and/or with the REVIEWERS listed for that module
and that backing out a checkin only requires an e
My vote is #2.
I would like to see a REVIEWERS file, and a general statement
that if you are going to make big changes you should discuss
it on -dev/IRC and/or with the REVIEWERS listed for that module
and that backing out a checkin only requires an even vote (that
is if you get a bad review you
Quick update:
It's been brought to my attention that CTR is basically the equivalent
to no-review. So, simplifying even further, there are only two types of
reviews, RTC and CTR.
CTR would mean that commits can be voted out, a CTR commit is the
equivalent of a request for a lazy consensus vo
[
https://issues.apache.org/jira/browse/TS-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak updated TS-142:
Attachment: ts-142-jp-v1.patch
Review opportunity although I think is small/superficial.
> read_from_middle_o
Hi all,
so, as far as I can tell, the consensus is to keep it "simple", and
there are (again, as far as I can tell) four possible policies. Let me
know if I have captured everyone's wishes.
Since I moved this over to -dev, just a quick summary: We're discussing
review and commit policies for
[
https://issues.apache.org/jira/browse/TS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Miles Libbey reassigned TS-223:
---
Assignee: Diane Smith
> preface.html needs a cleanup
>
>
> K
preface.html needs a cleanup
Key: TS-223
URL: https://issues.apache.org/jira/browse/TS-223
Project: Traffic Server
Issue Type: Improvement
Components: Documentation
Reporter: Miles Libbey
[
https://issues.apache.org/jira/browse/TS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak updated TS-222:
Attachment: ts-222-jp-v1.patch
Request for review.
This patch changes "overwrite" to be a generic "options" ar
[
https://issues.apache.org/jira/browse/TS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak resolved TS-70.
Resolution: Duplicate
Duping to TS-222 as I have a patch there.
> CacheProcessor::open_read etc should take an
Cache::open_write should use an options arg for flexability and shoudl allow
SYNC writes
Key: TS-222
URL: https://issues.apache.org/jira/browse/TS-222
Project: T
[
https://issues.apache.org/jira/browse/TS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839059#action_12839059
]
John Plevyak commented on TS-75:
I fixed part of this by making the flags identical for all the
[
https://issues.apache.org/jira/browse/TS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak resolved TS-114.
-
Resolution: Fixed
Fix Version/s: 2.1.0
This was fixed in -dev and is now in trunk.
> EventNames.cc us
[
https://issues.apache.org/jira/browse/TS-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak resolved TS-158.
-
Resolution: Fixed
This was fixed as part of the cache work in -dev which is now in trunk.
> cache should not
[
https://issues.apache.org/jira/browse/TS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak reassigned TS-114:
---
Assignee: John Plevyak
> EventNames.cc uses numbers instead of symbols to determine event names
> ---
21 matches
Mail list logo