[sage-devel] Re: trac naming convention for patches and bundles

2008-01-21 Thread Robert Bradshaw
On Jan 20, 2008, at 11:56 AM, mabshoff wrote: > > On Jan 20, 8:50 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: >> Nick Alexander wrote: > > Hi, > >>> On 20-Jan-08, at 9:18 AM, Jaap Spies wrote: Maybe it's a good thing to have a naming convention, say > > I am not to big a fan of this since I ke

[sage-devel] Re: trac naming convention for patches and bundles

2008-01-20 Thread mabshoff
On Jan 20, 8:50 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > Nick Alexander wrote: Hi, > > On 20-Jan-08, at 9:18 AM, Jaap Spies wrote: > >> Maybe it's a good thing to have a naming convention, say I am not to big a fan of this since I keep all my open source patches in another place and I do pre

[sage-devel] Re: trac naming convention for patches and bundles

2008-01-20 Thread Jaap Spies
Nick Alexander wrote: > > On 20-Jan-08, at 9:18 AM, Jaap Spies wrote: >> Maybe it's a good thing to have a naming convention, say > > I think so. I always attach my name, because I find it helps me keep > track of what I have been involved in and helps attribute patches. > You can always a

[sage-devel] Re: trac naming convention for patches and bundles

2008-01-20 Thread Nick Alexander
On 20-Jan-08, at 9:18 AM, Jaap Spies wrote: > > Hi, > > I see a lot of variation in naming: > > 1746.patch > 1653.hg > trac-1855.patch > trac_1715.patch > trac_1485_matrix-group_reverse_.patch > > Maybe it's a good thing to have a naming convention, say I think so. I always attach my name, bec