The other day I was looking for the fix to Jonesforth to make it run on modern Linux, but I couldn't find it amongst all the abandoned unfixed forks. I can't find things for all the worthless abandoned forks on Github. This isn't just Git it could happen with any other DVCS, but Git is where the culture is. More strongly, I'm recently finding Git culture with all its forking to be a real nuisance.
DOTBOT COPY FILE TO REPO CODE
Or if some automation was added to, say, pull all the code from all the sub-pages of an article and present it as files in zip or tar. It wouldn't help with viewing code in your editor, but that would be eased if code fields had a button to copy the text.
That way, anyone with a wiki account can edit them without additional tools. It might be more appropriate to create sub-pages for the code. I'll admit a few of these are a little obscure. I should have checked before posting the topic, but you can see them below: There's currently only a few wiki pages I could find that link to examples hosted as online source control resources. My thinking was that it would bring the code provided under shared control, which might help avoid 404's in the case that the hosting user removes their work, or allow for the code to evolve with the associated osdev wiki article. Or fully assembled examples in the case of the 'Bare Bones' series of articles.
Commonly this contains supplementary code.
My idea was intended to address the cases where users are already linking external repositories to the wiki. I didn't intend to introduce any new methodology for posting code to the wiki or sharing user projects. Then there's already places like Pastebin.Ĭreating / checking into a repository for the sole purpose of posting to OSDev sounds like a pretty nuisance for me. Either your source is open then you usually already have it residing in a publically accessible repository.
0 kommentar(er)
