savannah-cvs
[Top][All Lists]
Advanced

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

[Savannah-cvs] [59] Fixup whitespace before making more edits.


From: Bob Proulx
Subject: [Savannah-cvs] [59] Fixup whitespace before making more edits.
Date: Sun, 12 Jan 2014 04:47:01 +0000

Revision: 59
          http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=59
Author:   rwp
Date:     2014-01-12 04:46:55 +0000 (Sun, 12 Jan 2014)
Log Message:
-----------
Fixup whitespace before making more edits.

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

Modified: trunk/sviki/Git.mdwn
===================================================================
--- trunk/sviki/Git.mdwn        2013-10-28 20:54:47 UTC (rev 58)
+++ trunk/sviki/Git.mdwn        2014-01-12 04:46:55 UTC (rev 59)
@@ -4,7 +4,7 @@
 -------------
 
 git-core is backported on a regular basis using the procedure in
-infra/git.txt. Keep it up-to-date.
+infra/git.txt.  Keep it up-to-date.
 
 Repositories are in /subsystems/cvs/srv/git/project\_name.git for now.
 git+ssh is supported in Savane's sv\_membersh (delegates to git-shell).
@@ -89,8 +89,8 @@
 -----------------
 
 This needs some rationale and justification because during normal
-operation we never want to rewind a branch. It causes problems for
-anyone who has pulled from the branch. Normally branches only move
+operation we never want to rewind a branch.  It causes problems for
+anyone who has pulled from the branch.  Normally branches only move
 forward. But sometimes renaming a branch is the best solution to a
 problem.
 
@@ -118,10 +118,10 @@
       master
     * master-broken
 
-(There is likely a less heavy-handed command to do this. This is the
-only way I know how at this moment. I would welcome an improvement here.
+(There is likely a less heavy-handed command to do this.  This is the
+only way I know how at this moment.  I would welcome an improvement here.
 Normally with a working directory 'git checkout' would be used to set
-this.) The current branch reflog was moved when the branch was moved and
+this.)  The current branch reflog was moved when the branch was moved and
 is now set to master-broken and needs to be updated to point to master.
 Since this is a raw repository update the HEAD file directly:
 
@@ -133,9 +133,9 @@
     * master
       master-broken
 
-Verify that the change is correct. Better to leave the broken branch
+Verify that the change is correct.  Better to leave the broken branch
 around for a while than to remove it too soon and lose something that
-should not have been lost. Then clean up and discard the broken branch:
+should not have been lost.  Then clean up and discard the broken branch:
 
     GIT_DIR=/srv/git/exampleproject.git git branch -D master-broken
 
@@ -152,12 +152,12 @@
 >     which can be used to save bandwidth.
 
 -   Implement repository instanciation in Savane - more generally git
-    support. [Basic Git support implemented]
+    support.  [Basic Git support implemented]
 -   Repository optimization (packing, pruning) needs to be done at some
-    points, probably via hooks. git:// doesn't allow this kind of
-    operations. At kernel.org, people usually have shell access and a
+    points, probably via hooks.  git:// doesn't allow this kind of
+    operations.  At kernel.org, people usually have shell access and a
     private/non-shared repository, so they don't have this kind of
-    issues. The doc says: "packing every 4-5MB of loose objects
+    issues.  The doc says: "packing every 4-5MB of loose objects
     accumulation may be a good rule of thumb."
     
(http://www.kernel.org/pub/software/scm/git/docs/everyday.html\#Basic%20Repository).
     Apparently it's done by git when there's a lot of objects committed
@@ -188,5 +188,5 @@
 
 -   gitorious has pretty good git management interface which allow
     people to host cloned repos easily, but it lacks full project
-    management features like mailing list and trackers. If we can join
+    management features like mailing list and trackers.  If we can join
     the two, it would be unbeatable!




reply via email to

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