Re: [sage-devel] Re: Updating the Developer's Walk-Through

2011-02-23 Thread Robert Bradshaw
On Wed, Feb 23, 2011 at 10:13 AM, slabbe wrote: > Hi, > >> I'm going to still wait a few days before starting, so feel free to >> pile on if you would like to add to the discussion. > > At Sage Days 28, I gave a talk about how to contribute to Sage. The > philosophy I choose to present was to crea

Re: [sage-devel] Re: Updating the Developer's Walk-Through

2011-02-21 Thread D. S. McNeil
(1) I just started playing with this stuff, and found queues much nicer than cloning; it's worth It might be good to add a few explanations to the page of what to do in common-screwup cases (at least for me): e.g. unapplying everything (even though there are uncommitted changes), undoing an accid

Re: [sage-devel] Re: Updating the Developer's Walk-Through

2011-02-21 Thread David Kirkby
On 21 February 2011 10:36, Keshav Kini wrote: > I also wonder why the development guide recommends that we use > mercurial from inside a Sage session. It seems considerably more > tedious than just using it from the command line. Is there some > advantage I'm not seeing? > > -Keshav I would say