Update 2005-09-29 night.
Junio C Hamano committed
Sep 29, 2005 at 22:02 UTC
6dc88cc0dcda3b6654accc15e2b949b340fa4bfd
2 files changed
+63
-5
Porcelainistas
new
+56
@@ -0,0 +1,56 @@
1
+Message-ID: <20050927001542.GC15615@reactrix.com>
2
+From: Nick Hengeveld <nickh@reactrix.com>
3
+Date: Mon, 26 Sep 2005 17:15:42 -0700
4
+
5
+Good point - use of environment variables is more consistent. Use of
6
+command-line arguments is a bit more convenient in my case since I'm
7
+driving the transfer from a perl script, but I suppose consistency is
8
+more important...
9
+
10
+Message-ID: <000a01c5c2fe$71fd6200$0200a8c0@AMEER>
11
+From: "Ameer Armaly" <ameerarmaly@bellsouth.net>
12
+Date: Mon, 26 Sep 2005 20:57:33 -0400
13
+
14
+I am seriously looking at putting one together in the D language
15
+(http://www.digitalmars.com/d) <plug>, though it doesn't actually do
16
+anything as of yet, since I have to balance classes along with it.
17
+
18
+
19
+Message-ID: <1127840572.16026.29.camel@mariano>
20
+From: Mariano Videla <mvidela@ases.com.ar>
21
+Date: Tue, 27 Sep 2005 14:02:51 -0300
22
+
23
+I setup a git repository for gipy... Didn't upload any files in
24
+sourceforge because I don't think is ready.
25
+
26
+http://24.232.198.9:7978/gipy.git
27
+http://24.232.198.9:7978/cgi/gitweb.cgi
28
+
29
+
30
+Message-ID: <20050928113008.GA11309@snarc.org>
31
+From: tab@snarc.org (Vincent Hanquez)
32
+Date: Wed, 28 Sep 2005 13:30:08 +0200
33
+
34
+Well, I kinda work on one written in C using a libgit (using exec of git
35
+executable for the moment) It doesn't do that much at the moment:
36
+commiting, adding files, removing files.
37
+
38
+At some point I'ld like to have a very integrated and easy to use
39
+porcelain, but for now that's more a learning git by practice kind of
40
+project.
41
+
42
+Message-ID: <pan.2005.09.28.20.22.10.626793@smurf.noris.de>
43
+From: Matthias Urlichs <smurf@smurf.noris.de>
44
+Date: Wed, 28 Sep 2005 22:22:13 +0200
45
+
46
+Python integration needs either lots of fork+exec, a git rewrite in
47
+Python, or a libgit reorganization in library-ized C.
48
+
49
+I'm doing the latter, but my free time is kindof limited for now.
50
+
51
+My library-ize branch is at
52
+ git fetch http://netz.smurf.noris.de/git/git.git libize
53
+if anybody wants to have a look. My first goal is to get object access
54
+working sanely (because that's what I need for my Python project).
55
+
56
+I haven't merged up for some time, though.
TODO
+7
-5
@@ -114,11 +114,12 @@ Technical (heavier)
114
Technical (milder)
115
------------------
116
117
-* Use 'git-update-ref' in the scripts.
117
+* Use 'git-update-ref' in the scripts [DONE].
118
119
* Use symbolic refs in .git/HEAD. Should we do that everywhere
120
while honoring the symlinked HEAD in the existing repositories
121
for backward compatibility, or just only when 'ln -s' fails?
122
+ [DONE].
123
124
* Revisit 'git-merge'. It probably was a mistake to "loop to
125
choose the best one", since what is best is not ill defined to
@@ -201,16 +202,17 @@ Technical (milder)
202
Either adopt "only the first head is used for the merge by
203
default if taken from .git/remotes/ file", or "list heads to
204
merge on a separate Merge: line" proposal. I already have the
204
- code to do the former, so...
205
+ code to do the former, so... [DONE, open for improvement
206
+ patches but not just suggestions nor complaints.]
207
208
209
Technical (trivial)
210
-------------------
211
212
* Usher SSL enhancements to http-fetch from Nick Hengeveld into
211
- a shape acceptable by everybody.
213
+ a shape acceptable by everybody [DONE].
214
213
-* Require tk 2.4 in the spec file.
215
+* Require tk 2.4 in the spec file [DONE].
216
217
* show-branch naming heads is buggy [DONE].
218
@@ -218,7 +220,7 @@ Technical (trivial)
220
221
* 'git merge-projects'?
222
221
-* 'git clone' does not check things out. Should it?
223
+* 'git clone' does not check things out [DONE].
224
225
* 'git lost-and-found'? Link dangling commits found by
226
fsck-objects under $GIT_DIR/refs/lost-found/. Then