Re: [PATCH 4/8] trace: refactor to support multiple env variables

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH 4/8] trace: refactor to support multiple env variables

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:50:39

Jeff King [off-list ref] writes:
On Thu, Feb 24, 2011 at 10:25:04AM -0800, Junio C Hamano wrote:
...
So I guess I'm not sure what your complaint is.
There was no complaint. I wanted to see the reasoning behind the choices
you made spelled out (and later copied into developer docs).
I think I covered that pretty well above, but you lose the flexibility
of pushing different trace types to different places if you want to.
That statement illustrates the inflexibility that all packet traces going
to a same place rather clearly, doesn't it, though?  That "two-tier" thing
was my primary concern.

Re: [PATCH 4/8] trace: refactor to support multiple env variables

From: Jeff King <hidden>
Date: 2016-06-15 22:50:39

On Thu, Feb 24, 2011 at 11:44:13AM -0800, Junio C Hamano wrote:
Jeff King [off-list ref] writes:
quoted
On Thu, Feb 24, 2011 at 10:25:04AM -0800, Junio C Hamano wrote:
...
So I guess I'm not sure what your complaint is.
There was no complaint. I wanted to see the reasoning behind the choices
you made spelled out (and later copied into developer docs).
Oh. :) I'll write something up to go into Documentation/technical for my
re-roll. And something should clearly go in Documentation/git.txt for
users, too.
quoted
I think I covered that pretty well above, but you lose the flexibility
of pushing different trace types to different places if you want to.
That statement illustrates the inflexibility that all packet traces going
to a same place rather clearly, doesn't it, though?  That "two-tier" thing
was my primary concern.
Sorry, I don't quite understand what you're saying here.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help