The "targets" problem is stack is a bit more complicated; you're on
the right track.
A number of svn subcommands *should* take lists of targets. But they
don't right now, as you noticed.
What we need are some standardized routines which will:
* given a list of targets, "condense" the list, i.e. remove any item
from the list which is contained within another item
* given a condensed list of targets, calculate the longest common
ancestor path. This would be the path where we would start a
replace_root() (or begin_edit(), whatever we call it now).
If you'd like to implement these things, it would be great! We've put
them off until the filesystem is working.
Kevin Pilch-Bisson <kevin@pilch-bisson.net> writes:
> --M9NhX3UHpAaciwkO
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> Hi Karl, (and list),
>
> I'm addressing this to you(Karl), because I noticed that you had a note abo=
> ut
> it in STACK. There is a note in client/commit-cmd.c about passing
> TARGETs on down into svn_client_commit, and also something in the STACK
> about it. I have been playing around with a little Java GUI thing.
> (nowhere near usable), but I was thinking that this is actually a fairly
> important thing to do, soon. If you list multiple targets to a commit
> on the command line, the client will iterate over each of those targets,
> but use the same xml file each time. Thus only the last target is
> actually commited to the xml file.
>
> On a semi related note, is there a reason why we can't commit specific
> files, but only a directory at a time. I think that we really need the
> ability to commit a single file.=20
>
> If you want me to look at either of the above two things, let me know.
> I know you are a little busy with the filesystem stuff right now.
>
> --=20
> >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Kevin Pilch-Bisson
> kevin@pilch-bisson.net
> http://www.pilch-bisson.net
> PGP Public Key At http://pgp.pilch-bisson.net
>
> --M9NhX3UHpAaciwkO
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE6gBX4gJlk/lQdbnARAoJEAJoD10KQVibHaleyZxEqKs2ewBQs2wCZAfPo
> px4wtRvx5sJcy5jicQ7o8Oc=
> =D6WG
> -----END PGP SIGNATURE-----
>
> --M9NhX3UHpAaciwkO--
Received on Sat Oct 21 14:36:21 2006