Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no longer mention Bazaar following #1901 #1902

Merged
merged 2 commits into from
Sep 16, 2023
Merged

no longer mention Bazaar following #1901 #1902

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4cdcbe9
no longer mention Bazaar following #1901
aollier Sep 16, 2023
fae387e
removed Bazaar (bzr) from status.json
aollier Sep 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion book/01-introduction/sections/about-version-control.asc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Local VCSs suffer from this same problem -- whenever you have the entire history

(((version control,distributed)))
This is where Distributed Version Control Systems (DVCSs) step in.
In a DVCS (such as Git, Mercurial, Bazaar or Darcs), clients don't just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history.
In a DVCS (such as Git, Mercurial or Darcs), clients don't just check out the latest snapshot of the files; rather, they fully mirror the repository, including its full history.
Thus, if any server dies, and these systems were collaborating via that server, any of the client repositories can be copied back up to the server to restore it.
Every clone is really a full backup of all the data.

Expand Down
2 changes: 1 addition & 1 deletion book/01-introduction/sections/what-is-git.asc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Even though Git's user interface is fairly similar to these other VCSs, Git stor

The major difference between Git and any other VCS (Subversion and friends included) is the way Git thinks about its data.
Conceptually, most other systems store information as a list of file-based changes.
These other systems (CVS, Subversion, Perforce, Bazaar, and so on) think of the information they store as a set of files and the changes made to each file over time (this is commonly described as _delta-based_ version control).
These other systems (CVS, Subversion, Perforce, and so on) think of the information they store as a set of files and the changes made to each file over time (this is commonly described as _delta-based_ version control).

.Storing data as changes to a base version of each file
image::images/deltas.png[Storing data as changes to a base version of each file]
Expand Down
2 changes: 0 additions & 2 deletions status.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,11 +85,9 @@
},
"09-git-and-other-scms": {
"1-git-and-other-scms.asc": 0,
"sections/client-bzr.asc": 0,
"sections/client-hg.asc": 0,
"sections/client-p4.asc": 0,
"sections/client-svn.asc": 0,
"sections/import-bzr.asc": 0,
"sections/import-custom.asc": 0,
"sections/import-hg.asc": 0,
"sections/import-p4.asc": 0,
Expand Down