That sounds quite sensible to me.  Sometimes I make a patch before
opening a ticket, so the patch name does not have the ticket number on
it (e.g. #6386 opened yesterday).  But it would not be a bad thing if
I had opened the ticket first (to indicate that I was working on it)
so that I would have had the number available when creating the patch.

I like to be able to clear out all the patches which lie around on
various computers.  I know that any patch with a trac number on it
will exist on trac so can be deleted;  anything without a number is
more likely to be some work inprogress which I have saved from one
Sage build to carry on with on another, so I tend not to delete those.

John

2009/6/23 Nicolas M. Thiery <nicolas.thi...@u-psud.fr>:
>
>        Dear all,
>
> Apparently, there is a convention emerging to name systematically all
> patches on trac as trac_####_description.patch. I very much value this
> standardization attempt, especially in a period where things are
> getting automatized. We need it! In particular, I find it very useful
> to include the trac ticket number. On the other hand, let me argue
> about some inconveniences of the current naming scheme:
>
>  - The trac_ prefix does not bring any useful information.
>
>  - Starting the patch name with the ticket number defeats tab
>   completion when sorting through a large number of patches,
>   typically in a mercurial queue. It is a life saver for me to be
>   able to do hg qpop categories-fra<tab>
>
> Thoughs?
>
> For the record, here is the naming scheme we use in Sage-Combinat:
>
>  the_theme-the_description-ticket_number-author_initials.patch
>
> example:
>
>  categories-freemodule-6136-nt.patch
>
> Best,
>                                Nicolas
> --
> Nicolas M. ThiƩry "Isil" <nthi...@users.sf.net>
> http://Nicolas.Thiery.name/
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to