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

Re: raises hand for bite-sized issue #604

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-01-24 00:35:39 CET

Greg Stein <gstein@lyra.org> writes:
> The problem with trying to use Perl, or Daniel's "svn commit `foo.txt`"
> approach is that there are limits on the length of the command line.

Yeah, but the question is: has that actually been happening to people?
If yes, we should add the --list-o-files functionality. If not, let's
wait until it's a problem.

What Mark was describing (if I understand correctly) was not about
running into the command-line length limits.

-K

> I guess it might be possible to write a tool that directly calls exec() so
> that you can avoid the shell's command line length, but that problem is
> still there.
>
> Personally, I'd just say that if somebody has *that much* stuff checked out
> *and* it represents two or more logical commits, then they should have used
> a different working copy for one or more of those logical units.
>
> However, the simple fact remains that there are limits to the length of the
> command line. That limits the number of files/dirs that can be specified.
> Thus, having something like --file-list list-o-files.txt would be helpful.
>
> (and note: this would *only* be a long option; it would be *so* infrequent
> that it doesn't justify a short option name)
>
> Cheers,
> -g
>
> --
> Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:59 2006

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

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