git commit: TS-2628 Remove the wrong notification for not, to avoid spreading bad info.

2014-03-16 Thread zwoop
Repository: trafficserver Updated Branches: refs/heads/master d3fd1e674 - 4836e4e27 TS-2628 Remove the wrong notification for not, to avoid spreading bad info. Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo Commit:

Re: git commit: TS-2628 Remove the wrong notification for not, to avoid spreading bad info.

2014-03-16 Thread James Peach
On Mar 16, 2014, at 2:03 PM, zw...@apache.org wrote: Repository: trafficserver Updated Branches: refs/heads/master d3fd1e674 - 4836e4e27 TS-2628 Remove the wrong notification for not, to avoid spreading bad info. This seems fine for now, but as we discussed, the right fix is to make

Re: git commit: TS-2628 Remove the wrong notification for not, to avoid spreading bad info.

2014-03-16 Thread Leif Hedstrom
Yeah, I just wanted avoid further confusion as what ensued on IRC :) Also, Dynamic as denoted in RecordsConfig means it can be set with traffic line without restarts. So, unless we add another state, or something , it more feels this return value is not useful in this API? -- Leif On Mar

git commit: And it's another year ...

2014-03-16 Thread zwoop
Repository: trafficserver Updated Branches: refs/heads/master 4836e4e27 - 44eaddf5e And it's another year ... Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/44eaddf5 Tree: