On Wed, Jun 9, 2010 at 9:29 AM, Robert Bradshaw
wrote:
> On Jun 9, 2010, at 9:19 AM, Dr. David Kirkby wrote:
>
>> On 06/ 9/10 04:58 PM, Robert Bradshaw wrote:
>>>
>>> On Jun 9, 2010, at 7:29 AM, Dr. David Kirkby wrote:
>>>
I often find it annoying to be updating a standard package, only to
>>
On Jun 9, 2010, at 9:19 AM, Dr. David Kirkby wrote:
On 06/ 9/10 04:58 PM, Robert Bradshaw wrote:
On Jun 9, 2010, at 7:29 AM, Dr. David Kirkby wrote:
I often find it annoying to be updating a standard package, only to
find someone else is working on the same package, and so two people
produce
On 06/ 9/10 04:58 PM, Robert Bradshaw wrote:
On Jun 9, 2010, at 7:29 AM, Dr. David Kirkby wrote:
I often find it annoying to be updating a standard package, only to
find someone else is working on the same package, and so two people
produce patches and two different spkg files with the same ver
On Jun 9, 2010, at 7:29 AM, Dr. David Kirkby wrote:
I often find it annoying to be updating a standard package, only to
find someone else is working on the same package, and so two people
produce patches and two different spkg files with the same version
number.
I thought it would be usef
I often find it annoying to be updating a standard package, only to find someone
else is working on the same package, and so two people produce patches and two
different spkg files with the same version number.
I thought it would be useful if there was a way to indicate to other Sage
developer
