On Sep 11, 2007, at 1:18 PM, William Stein wrote:
>
> On 9/11/07, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>>> I would say that bundles are better than a number of patches that
>>> have
>>> to be applied manually one after the other. It is more painful to
>>> learn how to use bundles (I can tell because I still am not 100% on
>>> the finer points of merucrial like branching and so on), but in the
>>> end the workflow ends up much better. There was a video tutorial by
>>> William for SD4 I believe and I think it is only somewhere at
>>> sagemath.org, so use that as a starting point.
>>
>> Patches are much easier to read, but bundles are so much easier to
>> apply (especially if there are several of them, or there are non-
>> trivial dependancies). Ideally, one should be able to "open up" a
>> bundle and view it as a sequence of diffs online--does the mercurial
>> plugin for trac have such an ability? If not, it might be worth
>> adding (as both trac and mercurial are both python and open source).
>
> I very often do this:
>
> 1. Apply the bundle to some branch of my repository, and merge it in.
> But I *do not* check in the merge.
>
> 2. I browse the changes, build them, try them out, etc.
>
> 3. If I like the result I check it in. If not, I just do
> hg_sage.rollback()
> hg_sage.revert('--all')
> and it is as if I never applied the bundle.
Me too. It would be nice to be able to browse "into" bundles on trac
though. Wonder if this could be automated...
- Robert
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
