savannah-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [132] Fix paragraph formatting.


From: Bob Proulx
Subject: [Savannah-cvs] [132] Fix paragraph formatting.
Date: Wed, 11 Feb 2015 19:28:30 +0000

Revision: 132
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=132
Author:   rwp
Date:     2015-02-11 19:28:26 +0000 (Wed, 11 Feb 2015)
Log Message:
-----------
Fix paragraph formatting.

Modified Paths:
--------------
    trunk/sviki/UsingGit.mdwn

Modified: trunk/sviki/UsingGit.mdwn
===================================================================
--- trunk/sviki/UsingGit.mdwn   2015-02-11 18:49:10 UTC (rev 131)
+++ trunk/sviki/UsingGit.mdwn   2015-02-11 19:28:26 UTC (rev 132)
@@ -21,6 +21,7 @@
 
 Basic commands
 --------------
+
 -   Checkout:
 
         git clone git://git.sv.gnu.org/project.git
@@ -43,6 +44,7 @@
 
 Developer setup
 ---------------
+
 (For git 1.5.1 or newer)
 
 Your identity for when you push commits (strongly recommended):
@@ -58,6 +60,7 @@
 
 Developer basic commands
 ------------------------
+
 -   Create the initial directory and change to it:
 
         mkdir project_directory
@@ -109,6 +112,7 @@
 
 Shallow checkouts
 -----------------
+
 When bandwidth is an issue, people can download the latest version of
 your repository without downloading all the history, using "shallow
 checkouts". Note that such a copy has limitations, see
@@ -135,6 +139,7 @@
 
 git-cvsserver pserver compatibility
 -----------------------------------
+
 You can download a git repository using the CVS client, thanks to a
 pserver-compatible server from git:
 
@@ -155,6 +160,7 @@
 
 Importing from CVS
 ------------------
+
 Git comes with the tool, `git-cvsimport` which will import a CVS
 repository into a new git project. You may want to use this for
 converting your existing CVS repository to a new git repository.
@@ -187,6 +193,7 @@
 
 Importing from SVN
 ------------------
+
 Git comes with 2 SVN-related tools: `git-svnimport` and `git-svn`.
 `git-svnimport` is for importing revisions (a one-shot import, or
 incrementally); `git-svn` is a 2-way gateway to a SVN repository,
@@ -225,6 +232,7 @@
 
 Importing from GNU Arch
 -----------------------
+
 Use `git-archimport`.
 
 Example importing a project with a `project--main--1.0` main archive and
@@ -235,6 +243,7 @@
 
 Importing from CVS
 ------------------
+
 First thing you may want to do is to tag the state of your CVS
 repository and declare it as closed. For example:
 
@@ -296,6 +305,7 @@
 
 Pushing a Newly-Created, Existing, or Converted Git Repository
 --------------------------------------------------------------
+
 If you are importing a repository with tags, e.g. for past releases, use
 the --tags option to send them with the initial import:
 
@@ -323,6 +333,7 @@
 
 Removing a branch
 -----------------
+
 We don't really like this, but there's a way to remove remote branches.
 We don't like it because this allow project members to potentially
 remove free software from Savannah, willingly or by mistake. This is
@@ -341,6 +352,7 @@
 
 Non-Fast-Forward commits
 ------------------------
+
 'non-fast-forward' commits are commits which result in
 rewriting the commit history, leading to lost commits (see
 <http://git-scm.com/docs/git-push#_note_about_fast_forwards> for a technical
@@ -375,6 +387,7 @@
 
 Links
 -----
+
 -   repo.or.cz: hosting system similar to Savannah. Offers a public
     ''mob'' branch. The internals look a bit ad-hoc (lots of cron jobs
     that changes all permissions, privileges to Apache instead of a




reply via email to

[Prev in Thread] Current Thread [Next in Thread]