John A Meinel wrote:
> Maybe. The issue is that if you clone from remote into local, the path
> might actually need to change. Say I have:
If this API is a smart API, it will do the wrong thing sometimes. It
will no longer be suitable for making backup copies of branches with,
and it will no longer be suitable for cloning branches remotely.
So I propose making it a dumb API, and doing exactly what's requested.
Higher-level logic can decide how to handle these cases. I don't expect
copy_content_into to be smart.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel wrote:
> Maybe. The issue is that if you clone from remote into local, the path
> might actually need to change. Say I have:
If this API is a smart API, it will do the wrong thing sometimes. It
will no longer be suitable for making backup copies of branches with,
and it will no longer be suitable for cloning branches remotely.
So I propose making it a dumb API, and doing exactly what's requested.
Higher-level logic can decide how to handle these cases. I don't expect
copy_content_into to be smart.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://
iD8DBQFEt+ 8F0F+nu1YWqI0RA s11AJ9QcG8cG/ ac2PFEAsnEoySil eg+AwCffJcV Gio0Qcqo=
vne8PLPHOZxEHPH
=M3kq
-----END PGP SIGNATURE-----