Skip to content

Commit afa09ff

Browse files
committed
Remove references to Atlas.
The build is no longer performed by Atlas. We are on our own for publishing.
1 parent ed716b3 commit afa09ff

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

README.asc

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ Like the first edition, the second edition of Pro Git is open source under a Cre
88

99
A couple of things have changed since open sourcing the first edition.
1010
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.
1211

1312
We've also moved to keeping the translations in separate repositories rather than subdirectories of the English repository.
1413
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.
2019
The easiest way is simply to let us do it.
2120
A robot is standing by to look for new work on the main branch and automatically build it for everyone.
2221

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[].
2423

2524
The other way to generate e-book files is to do so manually with Asciidoctor.
2625
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.
4443

4544
Before signaling an issue, please check that there isn't already a similar one in the bug tracking system.
4645

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.
4847
The issue may have already been corrected, but the changes have not been deployed yet.
4948

5049
== Contributing

0 commit comments

Comments
 (0)