[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: Lawrence Kesteloot <lk_at_teamten.com>
Date: 2004-03-05 01:09:17 CET

>> % svn status | egrep '^M' | cut -c8-
>>
>>like:
>>
>> % svn commit -m Msg `svn status | egrep '^M.*Makefile' | cut -c8-`
>
> nevertheless:
> - status does not print all files (only modified or missing ones)

Oh, sorry, I thought the whole point was to show only modified files (so
that Makefiles not in the repository didn't result in "commit" errors).
  Maybe that was a different thread. You could try "status -v".

> - status requires server access ( to detect merge/conflicts )

Nope, it's all local as long as you don't use the -v flag.

> - not all windows-users have cygwin, egrep or similar tools installed
> (i know, its their own fault, I have it on my box:-)

True. If it's important enough a feature for you, though, you could
whip up a C program for it pretty easily. A program like Subversion
can't add a command-line flag for each specialized use or need, at least
when a wrapper script can fix the problem. You'd end up with dozens of
flags that are almost never used, and when your needs changed, even a
little, you'd be hosed again.

Lawrence

---------------------------------------------------------------------
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:08:20 2004

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