On Tue, Jun 14, 2022 at 06:47:58AM +0200, Gerhard Sittig wrote: [...] > The other issue is that manually patching the source to introduce > the non-operational skeleton, and then to manually copy in more > file content, which is not under version control, and is getting > lost in iterations, is tedious and non-reproducable. Would have > expected some addition of another remote, checkout of that > branch, and be done with two additional commands and no other > manual work involved. > > Another option would be to globally change the common prefix for > repos that are being fetched from at the start of the script, in > the tunables section. To not get the sigrok.org master but > somebody else's code base instead. Consistently as it is kept > there in a set of repos that belong to each other, similar to > what sigrok.org provides. The script is prepared to do that, it's > not (by design) prepared to run an arbitrary combination of > unrelated changes from different repos. Notice that this remote > repo might as well reside on your disk. Nobody said that a > network needs to be involved. > > I'm aware this is not your fault Dan for trying to follow these > instructions. It's the instructions that are weird and un-gitty
The best way from a user perspective is probably getting the changes into mainline; we are talking about a PR on a sigrok repo. ;) And yeah I know... Maybe it helps when Dan gets it to work and can confirm that it works as expected. > virtually yours > Gerhard Sittig Gruß Rene _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
