Karl Fogel wrote:
>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.
>
I've made commits from Windows where the command line was much longer
than 256 chars.
(Hmmm. that was from cygwin bash, so maybe the limit is in cmd.exe?)
>
>
>-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
>
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
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:37:00 2006