On Sep 11, 2007, at 3:20 PM, [EMAIL PROTECTED] wrote:
> On Tue, 11 Sep 2007, William Stein wrote:
>
>>
>> On 9/11/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>> wrote:
>>> I don't know why I haven't seen this before:
>>>
>>> hg_sage.inspect("...", options="-p")
>>>
>>> where ... can be the path / url of a patch / bundle /
>>> repository. It would seem that if there's a mercurial widget for
>>> trac, this feature may be added rather easily (if nonexistant).
>>>
>>
>> All inspect does is list the first line of the checkin comments on
>> what's in
>> the bundle. It doesn't actually tell you anything nontrivial
>> about what the
>> bundles actually contain. It's basically just the changelog.
>
> Ok. Now try it with options="-p".
Nice. One issue is that it seems it only operates within the context
of a given repository, i.e. I can't inspect random .hg files. Does
anyone know whether this is a limitation of inspect, or of the .hg
bundle itself?
- 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/
-~----------~----~----~----~------~----~------~--~---
