On Thu, Sep 06, 2007 at 04:13:39PM +0200, Charles Acknin wrote:
> On 9/5/07, Heikki Orsila <email@example.com> wrote:
> > Filed the issue.
> I think 'svn diff' is a more (the most?) appropriate sub-command to
> display the diffstat stuff, rather than 'svn log'.
> As for "2. git log -p shows commit patches", I'm not sure whether it
> would be most relevant in 'svn diff' or 'svn log' as it displays both
> unidiffs and commit metadata, but I'm leaning towards 'svn diff' since
> (a) the output is mostly made of unidiffs (b) the intent is to display
> a patch, as git-log(1) says (and as it looks like).
Right, but not necessarily a patch that you could apply - more a patch
for review. There's no reason you couldn't (for example) run 'svn log
--stop-on-copy --show-unidiff .../branches/foo' to review all work done
on a branch so far, as individual changes.
(For extra credit, I'd like a way to skip changes that were the result
of merges - can we do that already?).
Received on Thu Sep 6 16:58:25 2007
- application/pgp-signature attachment: stored