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

Re: Why do commands fail when a file is unknown to svn?

From: John Szakmeister <john_at_szakmeister.net>
Date: 2004-03-05 01:05:49 CET

On Thursday 04 March 2004 18:55, C.A.T.Magic wrote:
> ----- Original Message -----
> From: "Lawrence Kesteloot" <lk@teamten.com>
> To: <users@subversion.tigris.org>
> Cc: <dev@subversion.tigris.org>
> Sent: Friday, March 05, 2004 00:31
> Subject: Re: Why do commands fail when a file is unknown to svn?
>
> > > " status --without-the-single-characters-in-front "
> > > (ofcourse something shorter would be nice:)
> >
> > How about:
> >
> > % svn status | egrep '^M' | cut -c8-
> >
> > like:
> >
> > % svn commit -m Msg `svn status | egrep '^M.*Makefile' | cut -c8-`
> >
> > (untested)
> >
> > Lawrence
>
> nevertheless:
> - status does not print all files (only modified or missing ones)
> - status requires server access ( to detect merge/conflicts )

This second bullet is incorrect. 'svn status' doesn't require server access.
By default, it computes the status using information stored in the .svn/
directories. If you want it to compare against the server, you have
explicitly make that happen by using the -u or --show-updates switch. Either
way, status won't show you file that will conflict. It only shows files that
are in a conflicted state after a merge or update.

-John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 5 01:06:58 2004

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