Re: [Issue 2672] New - --show-log flag for "svn update"
I'm not in favor of this change. I don't believe that 'update' is the
appropriate place to be retrieving change log information. Thoughts?
On Sun, 03 Dec 2006, email@example.com wrote:
> Issue #|2672
> Summary|--show-log flag for "svn update"
> Status whiteboard|
> Issue type|ENHANCEMENT
> Subcomponent|cmdline client
> Assigned to|issues@subversion
> Reported by|salty_horse
> ------- Additional comments from firstname.lastname@example.org Sun Dec 3 12:01:49 -0800 2006 -------
> "svn up --show-log" will print the usual file modification output, and
> afterwards will print an "svn log"-style output of all the revisions between the
> current and the new one.
> This is an absolute nice-to-have. I can already get that information in a
> variety of ways, but the best one would be built into the client. Some of them:
> * running "svn info" to see the current revision, updating, and then running
> "svn log" against the old revision. I consider too much work - a wrapper script
> would fix that, but maybe other people would be interested in the feature.
> * following the commit emails. But these are useful for developers who like to
> review the code. As an end-user who uses a bleeding-edge application and simply
> likes to know "what's new since the last time I compiled", commit emails aren't
> the best solution.
Received on Mon Dec 4 18:55:41 2006
- application/pgp-signature attachment: stored
This is an archived mail posted to the Subversion Dev