| commit | ee2122992937d007bf25608c5915e635e0cc729d | |
| author | Junio C Hamano <gitster@pobox.com> | |
| Tue, 5 Jan 2010 07:55:57 +0000 (4 23:55 -0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 5 Jan 2010 07:55:57 +0000 (4 23:55 -0800) | ||
| tree | 9f0d8d7dc88c3c1d0b4b25d2a330ca03dd7ab546 | treesnapshot (tar.gz zip) |
| parent | 3f9558ac5f6ab9a6e2d2937ae12591b06568170e | commitdiff |
| parent | 99779d12076447d438225ec5dffa6355d1410b13 | commitdiff |
Merge in "What's cooking" history
The one-file-per-issue format is not an optimal way to maintain these
documents in a self-respecting version control system. Granted, they do
not "diff" very well, but that is something we can improve by defining a
custom diff driver for them.
"What's in" are just a glorified "git shortlog --no-merged" without any
additional comments, and I am very tempted to drop them. I haven't
issued them for quite some time, and nobody seems to have noticed.
The one-file-per-issue format is not an optimal way to maintain these
documents in a self-respecting version control system. Granted, they do
not "diff" very well, but that is something we can improve by defining a
custom diff driver for them.
"What's in" are just a glorified "git shortlog --no-merged" without any
additional comments, and I am very tempted to drop them. I haven't
issued them for quite some time, and nobody seems to have noticed.