On Thu, Apr 2, 2020 at 4:03 AM B Gillespie <ceilings...@gmail.com> wrote: > > I'm currently working on getting ticket 28252 fixed up for the current > developer branch, and I wanted to ask, what's the preferred method to rebase > a very old ticket? This was a project from Sage Days 99 in Minneapolis last > summer, so it currently is based on version 8.9.beta3 and is quite old. > > It's not a huge diff (just implements a couple of methods and adds relevant > literature references), so I was thinking it might make sense to make an > entirely new ticket and just copy the revisions to the relevant places in the > up-to-date codebase. Let me know if there's a better approach I should use.
no need to make a new ticket, unless the content in the ticket description is obsolete; you can just change the git branch. > > Thanks, > Bryan > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/06a6c08c-5920-4d82-9075-30ccdb8090cc%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1ZKQrbn4Nb_wkRbjTO70iCByoprE7mUNiG2%2B4JDQyLVg%40mail.gmail.com.
