TODO updates
Junio C Hamano committed
Feb 2, 2006 at 01:41 UTC
cc68633578c1c7f23fe249731a90eff94f17fda2
2 files changed
+45
-25
PU
+1
-1
@@ -78,4 +78,4 @@ do
78
(IFS=",$IFS"; git merge -n "Merge $H" pu $H) || exit
79
done
80
81
-(IFS=",$IFS"; git show-branch master $* pu $ORIG_HEAD)
81
+(IFS=",$IFS"; git show-branch master $* pu `git rev-parse --short $ORIG_HEAD`)
TODO
+44
-24
@@ -20,25 +20,26 @@ patch, perhaps ;-).
20
Documentation
21
-------------
22
23
-* Take the updated tutorial by Bruce Fields very seriously. It
24
- is a quite good initiative.
23
+* No pending issues at the moment. "Revamp Tutorial" initiative
24
+ by Bruce Fields ongoing and things are looking better.
25
26
27
Design issues
28
-------------
29
30
+* Rehash "git commit" with various parameters to be more
31
+ intuitive without breaking traditinal users too much. We need
32
+ to phase this in, especially if we are going to change "git
33
+ commit" to imply the current "git commit -a" behaviour.
34
+
35
+* "intent to add" index entries.
36
+
37
* Plug-in file-level merges. On the other hand, we may not even
38
need this; just tell people to run "xxdiff -U" on the working
39
tree files.
40
41
* Doing a merge in a separate directory.
42
36
-* Subprojects. I think the "bind commit" approach has been
37
- outlined at sufficiently detailed level. Maybe find time to
38
- actually start prototyping it?
39
-
40
- <7vacdzkww3.fsf@assigned-by-dhcp.cox.net>
41
-
43
* Make 'format-patch' take revision limiters similar to
44
rev-list. For example:
45
@@ -93,6 +94,39 @@ Technical (heavier)
94
Technical (milder)
95
------------------
96
97
+* Subprojects. I think the "bind commit" approach has been
98
+ outlined at sufficiently detailed level. Maybe find time to
99
+ actually start prototyping it?
100
+
101
+ <7vacdzkww3.fsf@assigned-by-dhcp.cox.net>
102
+
103
+* Shallow clones.
104
+
105
+* Mark entries as "assume unchanged" in the index.
106
+ New option to update-index to set or drop the bit is needed.
107
+
108
+ - update-index --no-stat paths...
109
+ - update-index --with-stat paths...
110
+
111
+ Also a config item '[core] trust_stat = false' would enable
112
+ this automatically:
113
+
114
+ - "update-index" with or without --add would mark the path
115
+ after registering. Should we make the working tree file
116
+ read-only at this point?
117
+
118
+ - checkout-index -u would mark the path and makes the working
119
+ tree file read-only.
120
+
121
+ Impacts to various commands:
122
+
123
+ - update-index --refresh would ignore them.
124
+
125
+ - diff-files would say unchanged.
126
+
127
+ - diff-index without --cached acts the same way as diff-index
128
+ --cached.
129
+
130
* Decide what to do about rebase applied to merged head. One
131
extreme is to allow rebase if "rev-list ours..theirs" gives
132
anything. This loosens the current merge-base based approach.
@@ -106,7 +140,7 @@ Technical (milder)
140
when both branches happen to have obtained the same set of
141
changes through different history. Not recording such keeps
142
the history simpler, and the next merge would soon create a
109
- true merge commit anyway, but does not feel quite right.
143
+ true merge commit anyway, but this does not feel quite right.
144
145
<20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
146
@@ -116,20 +150,6 @@ Technical (milder)
150
We need a timeline to force Porcelains to get ready. All the
151
major ones should be ready now.
152
119
-* Prepare to enable "most of the things are installed in
120
- GIT_EXEC_PATH not in bindir". I do not plan to set bindir !=
121
- gitexecdir myself in the main Makefile I ship, but distos
122
- should be able to choose to do so.
123
-
124
-* Forbid/ignore pack names that do not conform to the convention
125
- sha1_pack_name() assumes and reject in check_packed_git_idx()
126
- [In "pu"]
127
-
128
-* Any Porcelain-ish we forgot or punted to make usable from
129
- subdirectory? I think the last pass caught everything and
130
- what are remaining are whole-tree or whole repository
131
- operations.
132
-
153
* diff stopping at the first output; qgit wants to know if this
154
tree has any A or D from the other tree and nothing else.
155
Would help internal tree-diff in rev-list as well.
@@ -166,7 +186,7 @@ Technical (milder)
186
Technical (trivial)
187
-------------------
188
169
-* s/naked/bare/g.
189
+* Use parent info in 'diff-tree --stdin'.
190
191
* git-proxy should be spawned with sh -c 'command' $1 $2.
192