On Sunday, November 3, 2013 6:51:48 PM UTC-8, P Purkayastha wrote:
> If you check out the branch locally, you can run a
>
> git diff
>
> to see the cumulative changes.
>
That's good to know. However, when trying to figure out the history of
code, it's usually not so much the question what h
In researching python interfaces to opengl, I found a discussion from 2007
about using pyglet for 3D plotting in sage
(https://groups.google.com/forum/#!topic/sage-devel/AIyET83jB6A). But I
can find nothing beyond that to suggest why the project of incorporating
pyglet was dropped. (Pyglet is
On 11/04/2013 06:25 AM, Volker Braun wrote:
On Sunday, November 3, 2013 9:29:09 PM UTC, Nils Bruin wrote:
For purpose (b), however, it would be nicer if
The git log is easily accessible from code. Its easy to write all kinds
of analysis scripts if you care to.
If you check out the b
On Sunday, November 3, 2013 9:29:09 PM UTC, Nils Bruin wrote:
>
> For purpose (b), however, it would be nicer if
>
The git log is easily accessible from code. Its easy to write all kinds of
analysis scripts if you care to.
--
You received this message because you are subscribed to the Goo
It seems that the current "branch" field in trac serves two purposes:
(a) It's a pointer to code-in-development that people who are
collaborating can refer to
(b) It serves as the official "to-be-merged" code once the ticket has a
positive review
For purpose (a), having lots of little commits,
