On Tue, 13 Sep 2022, 08:57 'Travis Scrimshaw' via sage-devel, < sage-devel@googlegroups.com> wrote:
> > On Tuesday, September 13, 2022 at 4:14:26 PM UTC+9 Matthias Koeppe wrote: > >> On Tuesday, September 13, 2022 at 12:10:28 AM UTC-7 Travis Scrimshaw >> wrote: >> >>> How is the workflow that our current developers sometimes use >>>> irrelevant? Granted, this is a less used feature, but I believe it makes it >>>> harder to share branches privately. It has been useful for me in the past >>>> to have this (e.g., some hacked together code meant only to be shared with >>>> collaborators). >>>> >>> >> I think you'll have to explain what workflow is what you are talking >> about, and what your concern is. >> > > Let's say I want to solve the really hard problem of 2 + 2 for a paper we > are writing. So I write a branch that does the computation by repeatedly > adding 1: doing the computation 2 + 1 + 1. We don't plan to include this > into Sage as it is a horrible hack nor make it public because it will lead > to a proof of the Riemann Hypothesis (don't want to be scooped). Now you > also want to run computations or build some code off of it. How do you get > the code? We do not want to do a PR. With our current setup, I could push > the branch to the server, email you the branch name, and you could pull it. > Using GH, my understanding is we would have to share a repo and/or setup > push/pull rights, which seems more complicated > no, with GH you can just the same way email someone a branch name on your fork of the main repo, where is the problem here? (and what if I want to get stuff back from you too?). > same, you can pull a branch from someone's fork. PS. With git, one actually don't need any repos on servers, one can email branches around, this is the workflow of the Linux kernel project. It's not just patch-quilts, it is a mature system which used and checks hashes of commits in your branches. Cf. e.g. https://git-send-email.io/ > Does that clarify things? Admittedly I don't use it that often (and I am > willing to deal with such issues as they might arise later), but I don't > know about other practitioners at-large. > > -- > 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/05414f99-c449-4951-9f76-1d73175932c8n%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/05414f99-c449-4951-9f76-1d73175932c8n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAAWYfq38niCkZ2j9ThDs%3D%3D2jozEgg74sqO7gnVN5keye%2BEmm6A%40mail.gmail.com.
