On Thu, Jun 25, 2009 at 10:48 AM, Robert
Bradshaw<rober...@math.washington.edu> wrote:
>
> On Jun 25, 2009, at 1:37 AM, John Cremona wrote:
>
>> 2009/6/25 Jason Grout <jason-s...@creativetrax.com>:
>>>
>>> Robert Miller wrote:
>>>>>>> I think the following is a counterexample to "The trac_ prefix
>>>>>>> does
>>>>>>> not bring any useful information."
>>>>>> I still think it's not really, and it is just making the name
>>>>>> longer,
>>>>>> but I don't really care either.
>>>>> I don't see the use for it either, but it's not a huge issue for
>>>>> me.
>>>>
>>>> I should explain my workflow, as I'm probably not the only person
>>>> doing this (e.g. Craig). When I'm managing releases is one thing,
>>>> but
>>>> in daily practice, I always download patches to my home directory.
>>>> Think about it. Open a terminal, wget a patch, and this is what
>>>
>>> I presume that you're aware that hg qimport also takes http URLs and
>>> automatically downloads a patch and puts it onto the queue?  Ever
>>> since
>>> Carl showed that to me, I don't think I've downloaded any patch
>>> with wget.
>>>
>>
>> I did not know that, which will be useful.  What is the canonical
>> recipe for getting the patch's URL?  When I try I sometimes find I
>> have downloaded some html thing by mistake.
>
> At the bottom of the html view, there's a link entitled "original
> format" which gives the raw patch. It's the same as the html-view
> url, but with "attachment" replaced with "raw-attachment."
>

And it is a major pain to have to find that link every time you apply
a patch, imho.  I hate that. It's a design flaw in trac.
That's why I made
  sage: hg_sage.apply('any reasonable url into trac')
work...

William

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to