[Bro-Dev] Opinions on trace rewriter?
robin at icir.org
Tue Oct 26 09:07:26 PDT 2010
On Mon, Oct 25, 2010 at 22:51 -0700, you wrote:
> Only somewhat, because for this sort of capability (which I do get inquiries
> about time-to-time), telling folks that we removed it smacks of "it never
> really worked", which is more harsh than I think is deserved.
(At some point I was trying to figure out what the last version was
in which the rewriter "just worked" out of the box. I don't remember
the details anymore but I had to go back *very* far, and even then
there was still some trouble I can't recall right now.)
> In any case, I'm won over with the notion of having a coherent patch that
> captures what's been removed.
Ok. If we do the yanking in a separate branch, it should be pretty
easy to make a big patch for putting the stuff back in; we just need
to reverse the direction of the branch's diff I would think.
Once the next release is out, we can also create a tagged branch
1.6-with-rewriter that has the patch already applied. Then we can
just point people to it. That's even easier than keeping the patch
Robin Sommer * Phone +1 (510) 722-6541 * robin at icir.org
ICSI/LBNL * Fax +1 (510) 666-2956 * www.icir.org
More information about the bro-dev