I am new to git.
-
I am new to git.
Last night, I read the first three or so chapters of "Pro Git":
https://git-scm.com/book/en/v2
It has already been incredibly helpful, in terms of understanding the conceptual underpinnings of git, and how to use it in practice.
I haven't read anything else yet about git, so I can't offer a comparative perspective, but so far it treads that fine line between "too simple" and "too complicated" really well.
I love a good manual for software.
-
I am learning git for a specific project/reason.
But I can't help wonder if using it more broadly might be valuable, especially for work comprising text files with Markdown (rather than .odt/other documents).
It would be a massive change in workflow though, so not something to consider lightly.
-
@[email protected] as a warning, pretty much all git tooling only really works with text files. As soon as you start bringing in other stuff, images, spreadsheets, etc you'll spend more time fighting git than is reasonable. Soon you'll trip over a merge conflict in a binary file and you'll need to start doing stuff outside of git to figure out what should happen. (Two people edited this presentation, different slides but now git wants me to pick one of them because it doesn't understand how to merge the changes)
Never tried to do lots of complex documents, but I have tried to do game dev stuff and it sucks. -
@mindpersephone @neil that's why you store your presentations and documents as plain text markup
-
I do for presentations, but for documents that's not a realistic option for me.
-
GunChleocreplied to Neil Brown last edited by [email protected]
@neil @ianturton @mindpersephone In LibreOffice Writer, If you save as .fodt instead of .odt, you get a plain-text XML file.
Calc also has an .fods format.
Git is very powerful, but it also has a high learning curve.
