I'd actually be interested in knowing what the substitute for "git trac checkout ..." is. Because with trac, all ticket branches are present in the "trac" repository, you can pull anything from there. If I have to merge/pull from developer branch, do I need to add another remote to my local sage git repository? That sounds very laborious. Particularly for how to keep it up-to-date.
Note that sage trees are rather voluminous, so (some?) people tend to have not that many of them on their machine. If you're working on tickets that are relatively close to the current develop, it's quite doable to just check them in/out as you switch your work. I don't know how that would work if one needs multiple remotes. On Tuesday, 13 September 2022 at 01:03:59 UTC-7 Matthias Koeppe wrote: > On Tuesday, September 13, 2022 at 12:57:47 AM UTC-7 Travis Scrimshaw wrote: > >> With our current setup, I could push the branch to the server, email you >> the branch name, and you could pull it. >> > > So you're discussing a use case of the trac git server to share a branch > that has nothing to do with a trac ticket. > Doesn't sound like anything that needs a solution. > > > -- 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/a1e125fb-1f91-48c1-bf2e-aa675502528an%40googlegroups.com.
