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

RE: how to find what would be updated: status --show-updates not enough

From: Murli Varadachari <murli_at_yahoo-inc.com>
Date: 2006-10-12 20:28:27 CEST

> -----Original Message-----
> From: Joe Hannon [mailto:jhannon@SeattleMortgage.com]
> Sent: Thursday, October 12, 2006 11:17 AM
> To: users@subversion.tigris.org
> Subject: RE: how to find what would be updated: status --show-updates not
> enough
>
>
> On 10/12/06, Joe Hannon <jhannon@seattlemortgage.com> wrote:
>
> >>
> >> with a flag that tells you whether the updated file was added, deleted,
> updated, in conflict, or merged. I want to get this information without
> actually doing the updates. Confusingly, svn update --dry-run does not
> work. The mailing list taught me that the command is svn status --show-
> updates. However, svn status --show-updates tells you about what files in
> your working copy will be modified only. It won't say whether the
> modification is an update, delete, addition, etc. Is there a way to get
> this information without actually doing the update?
>
> >-----Original Message-----
> >From: Erik Huelsmann [mailto:ehuels@gmail.com]
>
> >svn status --show-updates --xml
>
> Thanks Erik,
>
> that helps. I'll need to parse this xml output today, but it would be
> cool if that information could be automatically output by svn status --
> show-updates in a future release, don't you think?
>
> Anyway, thanks again
> -j

This command also provides the necessary info ( especially the "conflicts"
)

svn merge --dry-run -r BASE:HEAD

cheers
murli

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 12 20:30:00 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.