Ah... git... indeed. Actually, any general notion of how version control works.
In the college where I study, people around all courses/degrees have the need for version control systems like git, although no course is being offered for that and they don't know what it is. I might offer an introduction to it next year depending on how much patience, time and money I have in my hands. ;) When I say "all courses/degrees", I really mean it. Even those seeking a Bachelor's degree in business administration, as is my case. ;) One of the things I like about git is that differentiation only works with plain text files by default. For me, this isn't a problem since I write documents, presentations and spreadsheets in Org mode (with some parts in LaTeX), and diagrams or other figures in TikZ. Sometimes I use Inkscape to draw to a .svg file or GNU Dia to the same effort, but I avoid both because I find them hard to remember the structure if I'm writting to them using a text editor, and because it's hard to remember their markup. There are ways to make git do differentiations with non-text files, and this does make sense with images in common formats (using ImageMagick, which marks the spots) and for .pdf (using diffoscope). But for other things --- including files from office suits/suites and multimedia projects --- attempting to differentiate stuff will probably be much easier by checking out the older version, copying it somewhere else, checking out "master" again, and opening both the old and new versions manually and having a detailed verification. [email protected] writes: > grep, sed, awk, diff and patch > > Looks like no one remembered git :) > > I'm open to help by giving gratis lessons on the above (or related) > topics - > I'm a teacher and I enjoy explaining stuff. :) > > But would be for helping Trisquel only? I'd like to contribute, but > I'm too busy with Parabola. > > I wanna learn C, mainly because I work a lot with kernels and Linux is > written in C. >
