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
Copy file name to clipboardExpand all lines: README.asc
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,6 @@ Like the first edition, the second edition of Pro Git is open source under a Cre
8
8
9
9
A couple of things have changed since open sourcing the first edition.
10
10
For one, we've moved from Markdown to the amazing Asciidoc format for the text of the book.
11
-
We've also moved to using O'Reilly's https://atlas.oreilly.com[Atlas platform] for generating continuous builds of the book so all major formats are always available in every language.
12
11
13
12
We've also moved to keeping the translations in separate repositories rather than subdirectories of the English repository.
14
13
See link:CONTRIBUTING.md[the Contributing document] for more information.
@@ -20,7 +19,7 @@ There are two ways to generate e-book content from this source code.
20
19
The easiest way is simply to let us do it.
21
20
A robot is standing by to look for new work on the main branch and automatically build it for everyone.
22
21
23
-
You can find the current builds on http://git-scm.com/book[] and more information about the builds available at https://progit.org[].
22
+
You can find the current builds on http://git-scm.com/book[].
24
23
25
24
The other way to generate e-book files is to do so manually with Asciidoctor.
26
25
If you run the following you _may_ actually get HTML, Epub, Mobi and PDF output files:
@@ -44,7 +43,7 @@ This uses the `asciidoctor`, `asciidoctor-pdf` and `asciidoctor-epub` projects.
44
43
45
44
Before signaling an issue, please check that there isn't already a similar one in the bug tracking system.
46
45
47
-
Also, if this issue has been spotted on the git-scm.com site, please cross-check that it is still present in the pdf version.
46
+
Also, if this issue has been spotted on the git-scm.com site, please cross-check that it is still present in this repo.
48
47
The issue may have already been corrected, but the changes have not been deployed yet.
0 commit comments