Michael Olson <[EMAIL PROTECTED]> writes: > Matthieu Moy <[EMAIL PROTECTED]> writes:
That is an interesting discussion. Let me try to express, why this functionality is useful for me. Using patches is an important feature when using tla with the following scenario: I use a development branch on computer A. I can mirror this archive to B. Now I make a small fix on B, send the changes via mail to A. Now I can apply the fix on A. I don't want to have a trace in the changelog or wherever that I did the fix on computer B. So this is the best solution for my problem there. This feature works very well for me. I do the change in B, send it to A. This undoes the changes on B also. On A I can apply the patch from B. I experimented a bit with bzr bundles for that purpose. The thing I don't like here is, that I can see that the patch is from B. Consider the following scenario: I do the main devolopment for DVC on my PC at home. I have installed DVC on several machines at work. Now I want to fix a little issue for DVC at work. The best solution for me is to send a patch to the machine at home. Then I use gnus to apply the patch. That functionality is not yet ready for bzr. But I will implement it, if Michael does not need that kind of functionality. In short, I like that functionality and I will use it often. I don't care, if we send patches or bundles. I am not sure, if it is possible to send a bundle for a not yet committed patch. Stefan. _______________________________________________ Dvc-dev mailing list [email protected] https://mail.gna.org/listinfo/dvc-dev
