Am 2014-11-16 um 12:27 schrieb Volker Braun: > On Sunday, November 16, 2014 6:34:56 AM UTC, Clemens Heuberger wrote: > > > Works for me, possibly because I have a newer git. > Can it be that it works for you because the commit > ec0aae9358f5204a3db6406b2c2f2818a78f5892 (this is the actual commit of > #16747) > is contained in your local repository? > > > Yes, and I have the commit visible because I ran "git remote update trac" (and > trac is not set up as tracking remote). This pulls down all branches, so in > particular it makes the commit visible again.
What is our policy concerning deleting branches from the trac repositories (e.g., I usually delete all branches on trac which are merged in a stable release, say, just to unclutter the name space there)? The current workflow (replacing the branch by the commit id when closing the ticket) suggests that the branch could be deleted at that stage; actually, it should only be deleted later (when the ticket is part of a release), because your workflow described above depends on that (well, ok, you do not do git remote update --prune trac). If the "merged in" field would be set when releasing a develop version, then the replacement of the branch name by the commit id in the ticket could occur at the same time (and not at the time when closing the ticket). Regards, CH -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
