You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for this great book on Git — this is the book I wish I had access to when I was learning Git.
I'm considering translating the book to English with some colleagues, and I wanted to share some thoughts regarding contents updates in translated editions.
I've noticed that the book carries its version information in the form "Version dated 7 June 2020", so I wanted to ask you if you could tag each new book release in some way — either using the date-stamp (e.g. 2020-06-07) or by adopting a version scheme like SemVer (e.g. v1.2.0) — so that anyone wishing to translate the book to other languages would be able to rely on Git tags to easily pin-point new book versions and track contents updates between each release.
Also, to simplify the task of integrating contents updates from the original German to other translations it would be quite useful if you included in the repository a single-file coalesced version of the AsciiDoc source for this purpose, which would then allow to easily diff-compare different editions to quickly pick-up changed contents (instead of having to diff each single chapter).
The text was updated successfully, but these errors were encountered:
First of all, thanks for this great book on Git — this is the book I wish I had access to when I was learning Git.
I'm considering translating the book to English with some colleagues, and I wanted to share some thoughts regarding contents updates in translated editions.
I've noticed that the book carries its version information in the form "Version dated 7 June 2020", so I wanted to ask you if you could tag each new book release in some way — either using the date-stamp (e.g.
2020-06-07
) or by adopting a version scheme like SemVer (e.g.v1.2.0
) — so that anyone wishing to translate the book to other languages would be able to rely on Git tags to easily pin-point new book versions and track contents updates between each release.Also, to simplify the task of integrating contents updates from the original German to other translations it would be quite useful if you included in the repository a single-file coalesced version of the AsciiDoc source for this purpose, which would then allow to easily diff-compare different editions to quickly pick-up changed contents (instead of having to diff each single chapter).
The text was updated successfully, but these errors were encountered: