Pre 1.4.0 updates to TODO to describe postponed items.
Junio C Hamano committed
Jun 8, 2006 at 14:03 UTC
53b13cb673f59b6d192c8a38671c00826e37b08e
2 files changed
+49
-32
TODO
+39
-28
@@ -17,58 +17,66 @@ if ever -- only if somebody cares enough and submits a clean
17
patch, perhaps ;-).
18
19
20
-UI
21
---
22
-
23
-* Make "git branch -d foo" while on foo branch suggest "maybe
24
- you want to go back to 'master'?"
25
-
26
-
20
Design issues
21
-------------
22
30
-* tree entries in index?
23
+* tree entries in index? -- sorry, stalled
24
32
-* "intent to add" index entries?
25
+* "intent to add" index entries? -- together with the above
26
+ needs rethinking.
27
28
* Plug-in file-level merges. On the other hand, we may not even
29
need this; just tell people to run "xxdiff -U" on the working
36
- tree files.
37
-
38
-* Doing a merge in a separate directory?
30
+ tree files (or kompare).
31
32
33
Technical (heavier)
34
-------------------
35
44
-* Maybe a pack optimizer.
45
-
46
- Given a set of objects and a set of refs (probably a handful
47
- branch heads and point release tags), find a set of packs to
48
- allow reasonably minimum download for all of these classes of
49
- people: (1) somebody cloning the repository from scratch, (2)
50
- somebody who tends to follow the master branch head reasonably
51
- closely, (3) somebody who tends to follow only the point
52
- releases.
53
-
54
- This needs a matching smart on the dumb protocol downloader.
55
-
36
* Libification. There are many places "run once" mentality is
37
ingrained in the management of basic data structures, which
58
- need to be fixed. [Matthias Urlichs is already working on
59
- this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>]
38
+ need to be fixed. [Matthias Urlichs was already working on
39
+ this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>, but I
40
+ do not know what happened to his efforts]
41
+
42
+* Lazy clones that can be controlled by the user, ranging from
43
+ totally on-demand a la CVS/SVN to "cache down to this old
44
+ commit so that I can make full use of git on at least recent
45
+ history". This need a lot of work in making tools to exit
46
+ gracefully when they hit unavailable objects while offline.
47
48
49
Technical (milder)
50
------------------
51
65
-* Shallow clones.
52
+* duplicated refspec given to "fetch-pack a a a" makes it emit
53
+ strange error message because it triggers the "match only
54
+ once" logic. Maybe strip the dups on the input side
55
+ (Uwe Zeisberger
56
+ <20060608073857.GA5072@informatik.uni-freiburg.de>).
57
+
58
+* upload-pack support for start fetching from any valid point on
59
+ the history, not just published refs. (Erik W. Biederman
60
+ <m164jc9ekx.fsf@ebiederm.dsl.xmission.com>)
61
+
62
+* git-daemon side support for virtual hosting. Client side
63
+ is ready in 1.4.0 (Jon Loeliger <1149610100.23938.75.camel@cashmere.sps.mot.com>).
64
+
65
+* teach git-upload-pack not to ack-continue early when the
66
+ client has roots it does not know about but it already has
67
+ learned the fork points for all the requested heads
68
+ (Ralf Baechle <20060524131022.GA11449@linux-mips.org>).
69
+
70
+* Per user .gitconfig across repositories -- ongoing.
71
72
* Encourage competition between annotate vs blame. Maybe come
73
up with some nontrivial test cases.
74
70
-* Subprojects. Try "gitlink".
75
+* Subprojects. Try "gitlink" -- sorry, stalled.
76
77
+* Rebase and checkout -m should be able to use recursive
78
+ strategy as well. These commands currently do not work across
79
+ renames.
80
81
* Decide what to do about rebase applied to merged head. One
82
extreme is to allow rebase if "rev-list ours..theirs" gives
@@ -108,6 +116,9 @@ Technical (trivial)
116
117
* git-proxy should be spawned with sh -c 'command' $1 $2.
118
119
+* Maybe a true git-proxy command that reads the first request
120
+ pkt-line, and redirects the request to its real destination.
121
+
122
* test scripts for the relative directory path stuff.
123
124
* In a freshly created empty repository, `git fetch foo:bar`
WI
+10
-4
@@ -4,6 +4,12 @@
4
maint_at=$(git rev-parse --verify refs/heads/maint)
5
master_at=$(git rev-parse --verify refs/heads/master)
6
7
+log () {
8
+ git log --no-merges "$@" |
9
+ git shortlog |
10
+ perl -pe 'if (!/^ / && !/^$/) { s/^/ / }'
11
+}
12
+
13
echo "To: git@vger.kernel.org"
14
echo "Subject: What's in git.git"
15
echo "X-maint-at: $maint_at"
@@ -16,7 +22,7 @@ then
22
echo
23
echo "* The 'maint' branch has these fixes since the last announcement."
24
echo
19
- git log --no-merges $tagged heads/maint | git shortlog
25
+ log $tagged heads/maint
26
fi
27
28
tagged=`git rev-parse --not --verify tags/sa/master`
@@ -26,7 +32,7 @@ then
32
echo
33
echo "* The 'master' branch has these since the last announcement."
34
echo
29
- git log --no-merges $tagged heads/master | git shortlog
35
+ log $tagged heads/master
36
fi
37
38
list=`git-rev-list refs/heads/master..refs/heads/next 2>/dev/null`
@@ -35,7 +41,7 @@ then
41
echo
42
echo "* The 'next' branch, in addition, has these."
43
echo
38
- git log --no-merges refs/heads/master..refs/heads/next | git shortlog
44
+ log heads/master..heads/next ^heads/cleannext
45
fi
46
47
list=`git-rev-list ^refs/heads/master ^refs/heads/next refs/heads/pu 2>/dev/null`
@@ -44,5 +50,5 @@ then
50
echo
51
echo "* The 'pu' branch, in addition, has these."
52
echo
47
- git log --no-merges ^refs/heads/master ^refs/heads/next refs/heads/pu | git shortlog
53
+ log ^heads/master heads/next..heads/pu
54
fi