Re: Re: limiting logs and diffs to specific nodes
From: Adam Monsen <haircut_at_gmail.com>
Date: 2006-09-19 01:01:12 CEST
Thank you for your reply. At this point I'd like to migrate this
For all you seeing this for the first time, I made a suggestion on the
For reference, here's the original thread on the "users" mailing list:
And here's the relevant issue that has been filed. It is resolved INVALID
On 9/18/06, Reedick, Andrew < Andrew.Reedick@bellsouth.com> wrote: [...]
> You might have better luck by showing precedence. The gnu diff in
Precedence? Did you mean preference? If so, I concur. I should get off my
This will take me some time; I need to read some source. I need to troll the
IMO, you would definitely need the --exclude-from=FILE to be useful.
Thank you for your suggestion.
And what pattern matching standard would you use? perl regex? OS
I think simple is good, so the idea would be that nodes (and their children,
And is 1.4.0's "svn diff --summarize" an adequate workaround? Get the
--summarize sounds nice! I hadn't heard of that, but I'll check it out. It
And what does it mean to filter out 'svn log --exclude .../lib'?
I'm confused... this isn't what I wrote. Please refer to my original example
Given that a single revision can contain changes to multiple directories,
I don't know how the implementation would work, but I don't think the fact
and how is it useful?
It's useful in the same way that "grep -r --exclude" is.
Given the plethora of filtering tools (perl, sed, grep, find, ksh, etc.)
For example, consider filtering out one directory (and its children) from a
I'm not saying it's a bad idea, but I do think it falls under "nice to
-- Adam MonsenReceived on Tue Sep 19 01:01:38 2006
This is an archived mail posted to the Subversion Dev mailing list.