@matheusbsbs / matheus-bagliano / commits / 4c78534341
Fork 0

Retire resolved items.

Junio C Hamano committed Aug 11, 2006 at 00:55 UTC 4c78534341e75d8b9f93b675562736bb1f51b13e
1 file changed -39
TODO
-39
@@ -49,10 +49,6 @@ Technical (heavier)
49 Technical (milder)
50 ------------------
51
52 -* git grep should be able to omit prefix when invoked from a
53 - subdirectory. Either make it an option or default with
54 - --full-name like ls-files does.
55 -
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
@@ -70,43 +66,8 @@ Technical (milder)
66 * git-daemon side support for virtual hosting. Client side
67 is ready in 1.4.0 (Jon Loeliger <1149610100.23938.75.camel@cashmere.sps.mot.com>).
68
73 -* teach git-upload-pack not to ack-continue early when the
74 - client has roots it does not know about but it already has
75 - learned the fork points for all the requested heads
76 - (Ralf Baechle <20060524131022.GA11449@linux-mips.org>).
77 -
78 -* Per user .gitconfig across repositories -- ongoing.
79 -
80 -* Encourage competition between annotate vs blame. Maybe come
81 - up with some nontrivial test cases.
82 -
69 * Subprojects. Try "gitlink" -- sorry, stalled.
70
85 -* Rebase and checkout -m should be able to use recursive
86 - strategy as well. These commands currently do not work across
87 - renames.
88 -
89 -* Decide what to do about rebase applied to merged head. One
90 - extreme is to allow rebase if "rev-list ours..theirs" gives
91 - anything. This loosens the current merge-base based approach.
92 - The other extreme is to refuse rebase if "rev-list
93 - theirs..ours" contains any merge commit, which was discussed
94 - on the list.
95 -
96 - <43CC695E.2020506@codeweavers.com>
97 -
98 -* Decide what the right thing to do upon an empty merge commit,
99 - when both branches happen to have obtained the same set of
100 - changes through different history. Not recording such keeps
101 - the history simpler, and the next merge would soon create a
102 - true merge commit anyway, but this does not feel quite right.
103 -
104 - <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
105 -
106 -* diff stopping at the first output; qgit wants to know if this
107 - tree has any A or D from the other tree and nothing else.
108 - Would help internal tree-diff in rev-list as well.
109 -
71 * daemon --strict-symlink.
72
73 * daemon --base-path does not apply automatically to whitelist