[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: diff summarize with wc path (was Re: [PATCH] svn diff --summarize)

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-02-08 00:03:42 CET

Martin Hauner wrote:
> Julian Foad wrote:
> >> $ svn diff --summarize
> >> svn: Summarizing diff can only compare repository to repository
> >
> > That might be considered an annoying limitation (of the API).
> Originally i planned to implement the other cases too... but
> since this is still an unreleased api i can't use in my client
> (which was my motivation to work on this) this issue didn't
> have much priority for me.. ;)

That's fair enough.

> Anyway, how would the rep<->wc case look like?

Do you mean the command syntax?

   svn diff --summarize -r100 wc/

Or the output? Just like the -rX:Y summary output.

Or the implementation? See below.

> I can imagine something like
> do a summarize rep<->base (would be simply the rep<->rep operation)
> somehow merge the summarize info with the status info to create
> the final summarize info.
> Maybe ignoring the local modifications and just doing the rep<->base
> would be near enough?

No: a rep<->base diff would be useful, but it wouldn't be near enough to a
rep<->WC diff to call it a rep<->WC diff.

> Thoughts?

Step 1: Allow X:BASE and BASE:Y summaries. This is easy: just resolve "BASE"
to the actual number; "COMMITTED" and "PREV" are already supported in this way.

Step 2: Implement a BASE:WC summary, performed without repository access. The
API should also allow WC:BASE, though the user interface doesn't. As a hack to
get this working, this could perhaps just call the full diff and discard the data.

Step 3: Allow X:WC and WC:Y summaries, probably by combining the info from (1)
and (2).

- Julian

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 8 00:04:17 2006

This is an archived mail posted to the Subversion Dev mailing list.