Jon Turney via Cygwin-apps writes: > Hmm... maybe this could be arranged better.
I wasn't talking about the push to the playground branch (which still contains my earlier commits) but that it reverted most of the cleanups. Takashi said it was too much work for him to reconcile with his changes, so that's that. Anyway, whoever becomes the new maintainer will have the say in what the package looks like. > The idea of playground branches was all a bit ad-hoc after I initially > had things configured to only allow pushes to master (or main, I > guess, now). I am fine with the idea of having a scratchpad branch that can vanish any moment. Any work that needs to be kept can be ion a separate repo (which actually there is for llvm, it's just local). > Perhaps it's possible to give every maintainer a branch only they can > create, push, force-push, rewind and delete? I have no idea how complicated that is to set up, but again, I'd rather just set up a new repo for that and publish it if it was of wider interest. > Or maybe I just need to allow branches named 'topic/*' which is the > convention used elsewhere on sourceware for volatile, personal > branches? The problem with these volatile branches is that they tend to fossilize, so I'm sitting on the fence on that question. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
