Skip to content

Commit 9487290

Browse files
committed
Rewrap intro: one sentence per line.
1 parent 931ec02 commit 9487290

File tree

1 file changed

+24
-8
lines changed

1 file changed

+24
-8
lines changed

en/book/book.asc

Lines changed: 24 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -8,14 +8,30 @@ Pro Git
88
[preface]
99
== Introduction
1010

11-
Welcome to the second edition of Pro Git. The first edition was published over four years ago now. Since then a lot has changed and yet many important things have not. While most of the core commands and concepts are still valid today as the Git core team is pretty fantastic at keeping things backward compatible, there have been some significant additions and changes in the community surrounding Git. The second edition of this book is meant to address those changes and update the book so it can be more helpful to the new user.
12-
13-
When I wrote the first edition, Git was still a relatively difficult to use and barely adopted tool for the harder core hacker. It was starting to gain steam in certain communities, but had not reached anywhere near the ubiquity it has today. Since then, nearly every open source community has adopted it. Git has made incredible progress on Windows, in the explosion of graphical user interfaces to it for all platforms, in IDE support and in business use. The Pro Git of four years ago knows about none of that. One of the main aims of this new edition is to touch on all of those new frontiers in the Git community.
14-
15-
The Open Source community using Git has also exploded. When I originally sat down to write the book nearly five years ago (it took me a while to get the first version out), I had just started working at a very little known company developing a Git hosting website called GitHub. At the time of publishing there were maybe a few thousand people using the site and just four of us working on it. As I write this introduction, GitHub is announcing our 10 millionth hosted project, with nearly 5 million registered developer accounts and over 230 employees. Love it or hate it, GitHub has heavily changed large swaths of the Open Source community in a way that was barely conceivable when I sat down to write the first edition.
16-
17-
I wrote a small section in Pro Git on GitHub as an example of hosted Git which I was never very comfortable with. I didn't much like that I was writing what I felt was essentially a community resource and also talking about my company in it. While I still don't love that conflict of interests, the importance of GitHub in the Git community is unavoidable. Instead of an example of Git hosting, I have decided to turn that part of the book into more deeply describing what GitHub is and how to effectively use it. If you are going to learn how to use Git then knowing how to use GitHub will help you take part in a huge community, which is valuable no matter which Git host you decide to use for your own code.
18-
11+
Welcome to the second edition of Pro Git.
12+
The first edition was published over four years ago now.
13+
Since then a lot has changed and yet many important things have not.
14+
While most of the core commands and concepts are still valid today as the Git core team is pretty fantastic at keeping things backward compatible, there have been some significant additions and changes in the community surrounding Git.
15+
The second edition of this book is meant to address those changes and update the book so it can be more helpful to the new user.
16+
17+
When I wrote the first edition, Git was still a relatively difficult to use and barely adopted tool for the harder core hacker.
18+
It was starting to gain steam in certain communities, but had not reached anywhere near the ubiquity it has today.
19+
Since then, nearly every open source community has adopted it.
20+
Git has made incredible progress on Windows, in the explosion of graphical user interfaces to it for all platforms, in IDE support and in business use.
21+
The Pro Git of four years ago knows about none of that.
22+
One of the main aims of this new edition is to touch on all of those new frontiers in the Git community.
23+
24+
The Open Source community using Git has also exploded.
25+
When I originally sat down to write the book nearly five years ago (it took me a while to get the first version out), I had just started working at a very little known company developing a Git hosting website called GitHub.
26+
At the time of publishing there were maybe a few thousand people using the site and just four of us working on it.
27+
As I write this introduction, GitHub is announcing our 10 millionth hosted project, with nearly 5 million registered developer accounts and over 230 employees.
28+
Love it or hate it, GitHub has heavily changed large swaths of the Open Source community in a way that was barely conceivable when I sat down to write the first edition.
29+
30+
I wrote a small section in Pro Git on GitHub as an example of hosted Git which I was never very comfortable with.
31+
I didn't much like that I was writing what I felt was essentially a community resource and also talking about my company in it.
32+
While I still don't love that conflict of interests, the importance of GitHub in the Git community is unavoidable.
33+
Instead of an example of Git hosting, I have decided to turn that part of the book into more deeply describing what GitHub is and how to effectively use it.
34+
If you are going to learn how to use Git then knowing how to use GitHub will help you take part in a huge community, which is valuable no matter which Git host you decide to use for your own code.
1935

2036
include::01-introduction/chapter1.asc[]
2137

0 commit comments

Comments
 (0)