Thanks to all.  I'll try out the import-patch tomorrow.  I will not
try to use sage-dev to attach to the ticket, I'll just push to trac
and update the trac fields myself.

John

On 17 December 2013 21:30, Travis Scrimshaw <tsc...@ucdavis.edu> wrote:
>>
>> This step, including the committing in git, can be done with
>>
>> sage --dev import-patch --url <URL>
>>
>> where <URL> can be the URL for the patch on trac (the raw one of course!).
>>
>
> You can also run "--local <path/to/file.patch>" instead of "--url <URL>" if
> you have the patch file on your computer.
>
> Best,
> Travis
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to