Spencer wrote:
> I'm curious about this too - looking at the github repo, it seems like 
> there's a mix of pulls into staging and into master. The git flow section of 
> https://genode.org/documentation/genode-foundations-24-05.pdf is a little 
> ambigious - it mentions staging as being the place to put untested changes 
> and then requests that topic branches be pulled from the most current 
> genodelabs/master.

Yes, as an outsider I find it hard to follow how they are dealing with pull 
requests/commits/issues. Hopefully we can get some clarification as I would 
like to add my own contributions to the project soon, but I don't know how to 
do it correctly.

> @Jack: I am in no way affiliated with the Genode team, so I don't claim to 
> speak for them, but I think it is unlikely that they will choose to convert 
> their README files to markdown as they are currently using a homebrew 
> formatting tool https://github.com/nfeske/gosh which has a few more features 
> including compiling to LaTeX.
> I agree that the code formatting looks prettier on github fwiw

Ah that makes a lot of sense! Thanks for letting me know. The README files did 
look like they had been written in some sort of syntax that I couldn't 
recognise. Github rendered them as plain text so I presumed it was just plain 
text with no actual file type. I will download Gosh and try it out on the 
genode repository to see how the pages look.

It would also make sense since I believe the Genode foundations book and the 
other books are written in LaTeX and PDF format, so the other documentation 
like the readme files would also be written in the same format.
_______________________________________________
users mailing list -- users@lists.genode.org
To unsubscribe send an email to users-le...@lists.genode.org
Archived at 
https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/message/C3HLJCNTVKWG2O7F345NR7QFKV2BVDIM/

Reply via email to