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: book/06-github/sections/4-managing-organization.asc
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Normally these accounts are used for Open Source groups (such as "`perl`" or "`r
12
12
An organization is pretty easy to create; just click on the "`+`" icon at the top-right of any GitHub page, and select "`New organization`" from the menu.
13
13
14
14
.The "`New organization`" menu item
15
-
image::images/neworg.png[The "`New organization`" menu item]
15
+
image::images/neworg.png[The “New organization” menu item]
16
16
17
17
First you'll need to name your organization and provide an email address for a main point of contact for the group.
18
18
Then you can invite other users to be co-owners of the account if you want to.
Copy file name to clipboardExpand all lines: book/09-git-and-other-scms/sections/client-svn.asc
+1-1
Original file line number
Diff line number
Diff line change
@@ -78,7 +78,7 @@ Subversion has to clone one revision at a time and then push it back into anothe
78
78
79
79
Now that you have a Subversion repository to which you have write access, you can go through a typical workflow.
80
80
You'll start with the `git svn clone` command, which imports an entire Subversion repository into a local Git repository.
81
-
Remember that if you're importing from a real hosted Subversion repository, you should replace the `file:///tmp/test-svn` here with the URL of your Subversion repository:
81
+
Remember that if you're importing from a real hosted Subversion repository, you should replace the `\file:///tmp/test-svn` here with the URL of your Subversion repository:
0 commit comments