Re: raises hand for bite-sized issue #604

On Tue, Jan 22, 2002 at 06:01:44PM -0600, Karl Fogel wrote:
> Mark Benedetto King <bking@answerfriend.com> writes:
> > Since it seems like a touchy issue, maybe, instead, we could have
> > a command line option that specifies a file that contains a list of files
> > to commit. This gives the functionality I want, without overloading
> > the $EDITOR functionality. I'd be happy to implement this (trivial)
> > option. Comments?
>
> -1
>
> Mark, I really think the problem you're having should be solved by
> tools already available. Run "svn status", transform the output as
> necessary, run commit on those arguments. This is something your
> editor or a perl script or something can do -- changing Subversion
> doesn't seem like the way to go to me.
>
> And yes, I do these things all the time, this isn't just
> theorizing. :-)

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.

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