summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-10-21 01:07:31 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-10-21 01:07:31 +0000
commit0914abaaafd5373f1bbbf40cea127f038cc1f7cb (patch)
tree3bb8b61436c3cf4111e497beac3c0b1515657b32
parent6578f3e847d67204d8e2011f6192ac4d13faf23b (diff)
A few comments. I think git-stash could be used now that it's available.
Also removed some stuff about the git support not being robust or well-tested, since it certainly is now.
-rw-r--r--doc/rcs/details.mdwn15
1 files changed, 10 insertions, 5 deletions
diff --git a/doc/rcs/details.mdwn b/doc/rcs/details.mdwn
index b9b3c7ead..3c9e465c2 100644
--- a/doc/rcs/details.mdwn
+++ b/doc/rcs/details.mdwn
@@ -125,12 +125,17 @@ I have been testing it for the past few days and it seems satisfactory. I
haven't observed any race condition regarding the concurrent blog commits
and it handles merge conflicts gracefully as far as I can see.
+(After about a year, git support is nearly as solid as subversion support --[[Joey]])
+
As you may notice from the patch size, GIT support is not so trivial to
-implement (for me, at least). Being a fairly fresh code base it has some
-bugs. It also has some drawbacks (especially wrt merge which was the hard
-part). GIT doesn't have a similar functionality like 'svn merge -rOLD:NEW
-FILE' (please see the relevant comment in mergepast for more details), so I
-had to invent an ugly hack just for the purpose.
+implement (for me, at least). It has some drawbacks (especially wrt merge
+which was the hard part). GIT doesn't have a similar functionality like
+'svn merge -rOLD:NEW FILE' (please see the relevant comment in `_merge_past`
+for more details), so I had to invent an ugly hack just for the purpose.
+
+> I was looking at this, and WRT the problem of uncommitted local changes,
+> it seems to me you could just git-stash them now that git-stash exists.
+> I think it didn't when you first added the git support.. --[[Joey]]
By design, Git backend uses a "master-clone" repository pair approach in contrast
to the single repository approach (here, _clone_ may be considered as the working