Even if you don't get textual diffs, merely keeping a history is a good
start to preserving documents.
And, btw, XML is not really any better than binary for doc storage because
you generally cannot merge it One of the reasons I hate those IDEs that
store project files in XLM.
On Tue, Dec 30,
On Tue, Dec 23, 2014 at 1:55 PM, Florian Coste wrote:
> Hello,
>
> Thank you for your answer ;) Other people said me yesterday on Git irc
> channel that .odt files are binary, and Git will not handle them correctly.
> I don't know DocBook XML, or Markdown, but after some research, I don't
> thin
Hello,
Thank you for your answer ;) Other people said me yesterday on Git irc
channel that .odt files are binary, and Git will not handle them correctly.
I don't know DocBook XML, or Markdown, but after some research, I don't
think this format will be easy for me to use it. Others people advised
Hello,
.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, ye
Hi,
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
