What's in 2009/05/01 (revised)
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
May 10, 2009 at 13:42 UTC
79b20516aae91510e15f1fe87c02c4b1f8f905dc
1 file changed
+29
-1
whats/cooking/2009/05/01.txt
+29
-1
@@ -23,9 +23,21 @@ meant to be merged to the maintenance series have "maint-" in their names.
23
* rr/forbid-bs-in-ref (Fri May 8 07:32:37 2009 +0200) 1 commit
24
+ Disallow '\' in ref names
25
26
+This retroactively forbids use of what people could have been using
27
+happily, which, strictly speaking, is a no-no, but makes sense in the
28
+longer term.
29
+
30
* jk/maint-add-empty (Tue Apr 28 23:21:01 2009 -0400) 1 commit
31
- add: don't complain when adding empty project root
32
33
+When you say "git add ." in an empty directory, you get "No path matches
34
+''", instead of "No path matches '.'", and this "fixes" it by hiding the
35
+error and making the command silently succeed. Strictly speaking it
36
+introduces inconsistency, but I think an empty directory is so
37
+uninteresting special case that not signalling it as an error is Ok.
38
+
39
+Will merge to 'next'.
40
+
41
* lt/maint-diff-reduce-lstat (Sat May 9 15:11:17 2009 -0700) 2 commits
42
+ Teach 'git checkout' to preload the index contents
43
+ Avoid unnecessary 'lstat()' calls in 'get_stat_data()'
@@ -59,6 +71,9 @@ meant to be merged to the maintenance series have "maint-" in their names.
71
+ parseopt: add OPT_NEGBIT
72
+ parseopt: add OPT_NEGBIT
73
74
+I somehow botched the commit log message of the top one; it is about
75
+fixing "ls-files --no-empty-directory".
76
+
77
* fl/git-pm (Thu May 7 15:41:28 2009 +0200) 2 commits
78
+ Git.pm: Always set Repository to absolute path if autodetecting
79
+ Git.pm: Set GIT_WORK_TREE if we set GIT_DIR
@@ -152,6 +167,8 @@ in binary mode as well.
167
- rev-list: refactor printing bisect vars
168
- rev-list: make "estimate_bisect_steps" non static
169
170
+Will merge to 'next'.
171
+
172
* mh/show-branch-color (Sat Apr 25 13:46:14 2009 +0200) 2 commits
173
+ bash completion: show-branch color support
174
+ show-branch: color the commit status signs
@@ -162,9 +179,13 @@ in binary mode as well.
179
* ar/merge-one-file-diag (Wed Apr 29 23:40:50 2009 +0200) 1 commit
180
- Clarify kind of conflict in merge-one-file helper
181
182
+Will merge to 'next'.
183
+
184
* mh/diff-stat-color (Sat Apr 25 00:06:47 2009 +0200) 1 commit
185
- diff: do not color --stat output like patch context
186
187
+Will merge to 'next'.
188
+
189
* rc/http-push (Sat Apr 25 00:35:57 2009 +0800) 3 commits
190
- http-push: send out fetch requests on queue
191
- t5540-http-push: test fetching of packed objects
@@ -179,9 +200,13 @@ in binary mode as well.
200
- Introduce an unlink(2) wrapper which gives warning if unlink
201
failed
202
203
+Will merge to 'next'.
204
+
205
* ph/submodule-rebase (Fri Apr 24 09:06:38 2009 +1000) 1 commit
206
- git-submodule: add support for --rebase.
207
208
+Will merge to 'next'.
209
+
210
* mw/send-email (Mon Apr 13 13:23:52 2009 -0500) 6 commits
211
- send-email: Remove superfluous `my $editor = ...'
212
- send-email: 'References:' should only reference what is sent
@@ -194,6 +219,8 @@ in binary mode as well.
219
Only partially queued, but this is not 1.6.3 material and we are not in a
220
hurry.
221
222
+Will merge to 'next'.
223
+
224
* js/add-edit (Mon Apr 27 19:51:42 2009 +0200) 2 commits
225
+ t3702: fix reliance on SHELL_PATH being '/bin/sh'
226
+ git-add: introduce --edit (to edit the diff vs. the index)
@@ -228,4 +255,5 @@ command line would not work very well with this series.
255
push
256
257
These are for 1.7.0, but the messages when they trigger together may need
231
-to be rethought.
258
+to be rethought. Will start merging them to 'next' shortly.
259
+