Matthias, people have their own workflows that evolved around using trac for a long time. It is only natural that there are now questions of how these workflows will look like when using github. We should give space to such questions following the spirit of "there are no stupid questions". Especially since Travis made it clear that its not a hard requirement for him to send branches around by email but that he is wondering weather this would still be helpful.
On Tuesday, 13 September 2022 at 10:17:58 UTC+2 Matthias Koeppe wrote: > All, let's please not expand the discussion of exotic workflows. > > Sharing files, sharing branches etc. is a solved problem, with multiple > easy solutions. This is not 2005 any more, when having an SVN server was > the gold standard to sharing & versioning files. > > > On Tuesday, September 13, 2022 at 1:03:59 AM 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/eb743bc1-9e89-4f0f-9cb5-0b7fc6d1bfa7n%40googlegroups.com.
