.odt files (I assume you are talking about OpenOffice documents) are
binary, and as such, Git doesn't handle them very well. If you want to
manage such documents in Git, you must use a textual format, such as
DocBook XML or Markdown.
Now that we are here, to answer your other questions, yes, I do manage my
tech papers, novels, API documentations and pretty much every text is Git.
But once again, these are textual files (most of them are DocBook XMLs).
Even the Pro Git book's sources are versioned in Git :-)
On 23 Dec 2014 16:44, "Florian Coste" <fcost...@gmail.com> wrote:
> I'm a recently user of Git. I think it's a great tool for development
> project ;) I've already used it on university project, but, in practise,
> we've worked without it, badly...
> Recently I started to read documentation because I wanted to join open
> source projects on Github. And I had one idea. I'm wondering if Git could
> be use for other things ? For example, I would like to use Git for my CV's
> redaction. Indeed, it would be interesting to have different versions of my
> CV, and having the possibility to get an older version.
> Have you no-traditional use of Git ? Which ? What do you think about my
> project ? Git will need process .odt files. Maybe, it would be better to
> use graphical uses for making diff between two versions, don't you think ?
> Thank you so much.
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.