I don't think it is feasible to solve the general Quilt to other VCS interaction problem solely within Quilt. What would help a lot is if there were an actual public API that tools like my q4 script could use instead of using the Quilt CLI and dealing with the ambiguities it presents.
On Sun, Dec 13, 2009 at 04:22, Hugo Mills
<address@hidden> wrote:
I think this may have slipped through a crack... any comments?
Hugo.
On Thu, Nov 26, 2009 at 08:32:54PM +0000, address@hidden wrote:
> It's useful when using quilt in conjunction with another version
> control system to hand off patches from quilt's management to that of
> the other VCS. This quilt function provides that capability.
>
> Any patch in the stack can be sent to the VCS, provided that no
> earlier patch also touches the same files. The commit message is taken
> from the quilt patch header. A range of patches can be committed in
> sequence, if desired.
>
> Only subversion (and a "null", forgetful VCS) are implemented in
> this version, although I have left stubs in the code for git and
> mercurial. The code attempts to determine automatically which VCS to
> use, and will complain (and stop) if none or more than one is found.
--
=== Hugo Mills: address@hidden carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Debugging is like hitting yourself in the head with hammer: ---
it feels so good when you find the bug, and you're
allowed to stop debugging. -- PotatoEngineer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLJNx9IKyzvlFcI40RAt8OAJ9kTcrtCLXk8YXaLk+k1WD7UKrx8QCg1GpV
3Q07IphDjsWiNt4BJ1oC2EM=
=PgH0
-----END PGP SIGNATURE-----
_______________________________________________
Quilt-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/quilt-dev
--
Kurtis Rader
Caretaker of the exceptional canines Einstein and Chino
http://big.corp.google.com/~krader/notes/
+1 650-214-4244