@@ -17,45 +17,23 @@ if ever -- only if somebody cares enough and submits a clean
1717patch, perhaps ;-).
1818
1919
20- Documentation
21- -------------
22-
23- * No pending issues at the moment. "Revamp Tutorial" initiative
24- by Bruce Fields ongoing and things are looking better.
25-
26-
2720UI
2821--
2922
3023* Make "git branch -d foo" while on foo branch suggest "maybe
3124 you want to go back to 'master'?"
3225
33- * Error message from "git checkout -b bar v2.6.10" should assume
34- v2.6.10 is an attempt to switch to a new branch based on
35- mistyped tag, not an attempt to revert path v2.6.10 from the
36- HEAD commit with extra "make and switch to this branch"
37- argument.
38-
39- * "git commit [-i|-o] paths..." with misspelled paths would be
40- silently ignored. Add a flag to ls-files to catch unmatched
41- pathspec to prevent this.
42-
4326
4427Design issues
4528-------------
4629
47- * Rehash "git commit" with various parameters to be more
48- intuitive without breaking traditinal users too much. We need
49- to phase this in, especially if we are going to change "git
50- commit" to imply the current "git commit -a" behaviour.
51-
52- * "intent to add" index entries.
30+ * "intent to add" index entries?
5331
5432* Plug-in file-level merges. On the other hand, we may not even
5533 need this; just tell people to run "xxdiff -U" on the working
5634 tree files.
5735
58- * Doing a merge in a separate directory.
36+ * Doing a merge in a separate directory?
5937
6038* Make 'format-patch' take revision limiters similar to
6139 rev-list. For example:
@@ -101,52 +79,21 @@ Technical (heavier)
10179
10280 This needs a matching smart on the dumb protocol downloader.
10381
104- * Maybe an Emacs VC backend.
105-
106- * Look at libified GNU diff CVS seems to use, or libxdiff.
107- [Daniel has his own diff tool almost ready to start
108- integrating and testing]
109-
11082
11183Technical (milder)
11284------------------
11385
114- * "git status -v" to give commit preview.
86+ * Shallow clones.
87+
88+ * Encourage competition between annotate vs blame. Maybe come
89+ up with some nontrivial test cases.
11590
11691* Subprojects. I think the "bind commit" approach has been
11792 outlined at sufficiently detailed level. Maybe find time to
11893 actually start prototyping it?
11994
12095 <7vacdzkww3.fsf@assigned-by-dhcp.cox.net>
12196
122- * Shallow clones.
123-
124- * Mark entries as "assume unchanged" in the index.
125-
126- <Pine.LNX.4.64.0601311807470.7301@g5.osdl.org>
127-
128- A config item '[core] trust_stat = false' would cause to:
129-
130- - "update-index" with or without --add would mark the path
131- valid after registering. Should we make the working tree
132- file read-only at this point?
133-
134- - checkout-index -u would mark the path and makes the working
135- tree file read-only.
136-
137- - read-tree without -u would mark the path invalid.
138-
139- - update-index --refresh should *not* mark up-to-date paths valid.
140-
141- Impacts to various commands:
142-
143- - update-index --refresh would ignore them.
144-
145- - diff-files would say unchanged.
146-
147- - diff-index without --cached acts the same way as diff-index
148- --cached.
149-
15097* Decide what to do about rebase applied to merged head. One
15198 extreme is to allow rebase if "rev-list ours..theirs" gives
15299 anything. This loosens the current merge-base based approach.
@@ -164,8 +111,6 @@ Technical (milder)
164111
165112 <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
166113
167- * Perhaps a smarter HTTP anonymous download via CGI.
168-
169114* diff stopping at the first output; qgit wants to know if this
170115 tree has any A or D from the other tree and nothing else.
171116 Would help internal tree-diff in rev-list as well.
@@ -179,22 +124,11 @@ Technical (milder)
179124* Perhaps detect cloning request in upload-pack and cache the
180125 result for next cloning request until any of our refs change.
181126
182- * Perhaps accept patch to optionally allow '--fuzz' in
183- 'git-apply'. am/applymbox is _not_ the place to do it.
184-
185- * Allow 'git apply' to accept GNU diff 2.7 output that forgets
186- to say '\No newline' if both input ends with incomplete
187- lines.
188-
189127* Perhaps deal with "Files differ" (binary diff) in non C
190128 locales.
191129
192130* Maybe grok PGP signed text/plain in applymbox as well.
193131
194- * Output full path in the "git-rev-list --objects" output, not
195- just the basename, and see the improved clustering results in
196- better packing [Tried, but did not work out well].
197-
198132
199133Technical (trivial)
200134-------------------
0 commit comments