Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

small improvements to introduction #193

Closed
wants to merge 1 commit into from

3 participants

@dominiqueplante

...u have to be online to do a lot of version control related things with SVN or similar systems. You don't for Git

@dominiqueplante dominiqueplante small formatting improvements, expand on why Git is better than SVN -…
… you have to be online to do a lot of version control related things with SVN or similar systems. You don't for Git
859f7fc
@jnavila jnavila commented on the diff
en/01-introduction/01-chapter1.markdown
@@ -28,7 +32,7 @@ Figure 1-2. Centralized version control diagram.
This setup offers many advantages, especially over local VCSs. For example, everyone knows to a certain degree what everyone else on the project is doing. Administrators have fine-grained control over who can do what; and it’s far easier to administer a CVCS than it is to deal with local databases on every client.
-However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything—the entire history of the project except whatever single snapshots people happen to have on their local machines. Local VCS systems suffer from this same problem—whenever you have the entire history of the project in a single place, you risk losing everything.
+However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything—the entire history of the project except whatever single snapshots people happen to have on their local machines. Local VCS systems suffer from this same problem—whenever you have the entire history of the project in a single place, you risk losing everything. To take full advantage of these centralized servers, you must also be online. You can't do commits, view history on a file, or do other interesting source control related operations when you are offline. However, with Git, most of the useful source control operations you would want to do are available even when you are offline.
@jnavila Collaborator
jnavila added a note

Not sure this is the right place to start talking about the advantages of distributed version control. It is the next section's content.

And I think it is too early to start introducing the word "commit"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
@zachlatta

This change seems redundant. "If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes" seems to cover what's added.

@jnavila jnavila closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 23, 2012
  1. @dominiqueplante

    small formatting improvements, expand on why Git is better than SVN -…

    dominiqueplante authored
    … you have to be online to do a lot of version control related things with SVN or similar systems. You don't for Git
This page is out of date. Refresh to see the latest.
Showing with 7 additions and 3 deletions.
  1. +7 −3 en/01-introduction/01-chapter1.markdown
View
10 en/01-introduction/01-chapter1.markdown
@@ -1,6 +1,10 @@
# Getting Started #
-This chapter will be about getting started with Git. We will begin at the beginning by explaining some background on version control tools, then move on to how to get Git running on your system and finally how to get it setup to start working with. At the end of this chapter you should understand why Git is around, why you should use it and you should be all setup to do so.
+This chapter will be about getting started with Git. We will begin at the beginning by explaining some background on version control tools, then move on to how to get Git running on your system and finally how to get it setup to start working with. At the end of this chapter you should understand:
+* Why Git is around
+* Why you should use Git
+
+You should also be all setup to start using Git on your machine.
## About Version Control ##
@@ -10,7 +14,7 @@ If you are a graphic or web designer and want to keep every version of an image
### Local Version Control Systems ###
-Many peoples version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or copy over files you don’t mean to.
+Many people's version-control method of choice is to copy files into another directory (perhaps a time-stamped directory, if they’re clever). This approach is very common because it is so simple, but it is also incredibly error prone. It is easy to forget which directory you’re in and accidentally write to the wrong file or copy over files you don’t mean to.
To deal with this issue, programmers long ago developed local VCSs that had a simple database that kept all the changes to files under revision control (see Figure 1-1).
@@ -28,7 +32,7 @@ Figure 1-2. Centralized version control diagram.
This setup offers many advantages, especially over local VCSs. For example, everyone knows to a certain degree what everyone else on the project is doing. Administrators have fine-grained control over who can do what; and it’s far easier to administer a CVCS than it is to deal with local databases on every client.
-However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything—the entire history of the project except whatever single snapshots people happen to have on their local machines. Local VCS systems suffer from this same problem—whenever you have the entire history of the project in a single place, you risk losing everything.
+However, this setup also has some serious downsides. The most obvious is the single point of failure that the centralized server represents. If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they’re working on. If the hard disk the central database is on becomes corrupted, and proper backups haven’t been kept, you lose absolutely everything—the entire history of the project except whatever single snapshots people happen to have on their local machines. Local VCS systems suffer from this same problem—whenever you have the entire history of the project in a single place, you risk losing everything. To take full advantage of these centralized servers, you must also be online. You can't do commits, view history on a file, or do other interesting source control related operations when you are offline. However, with Git, most of the useful source control operations you would want to do are available even when you are offline.
@jnavila Collaborator
jnavila added a note

Not sure this is the right place to start talking about the advantages of distributed version control. It is the next section's content.

And I think it is too early to start introducing the word "commit"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
### Distributed Version Control Systems ###
Something went wrong with that request. Please try again.