|
1 | 1 | To: git@vger.kernel.org |
2 | | -Subject: What's cooking in git.git (Feb 2010, #01; Wed, 03) |
3 | | -X-master-at: 07cf0f2407709e3764ea989696b513ec32613504 |
4 | | -X-next-at: 9253ab096ff0b88d2d690152c03d9e2491d5c40c |
| 2 | +Subject: What's cooking in git.git (Feb 2010, #02; Sun, 07) |
| 3 | +X-master-at: 8051a030617cf7d083568cca223bdaa15052c33f |
| 4 | +X-next-at: 2ac040d3d8b263430781e605b7b87a06cbc1e0f0 |
5 | 5 |
|
6 | | -What's cooking in git.git (Feb 2010, #01; Wed, 03) |
| 6 | +What's cooking in git.git (Feb 2010, #02; Sun, 07) |
7 | 7 | -------------------------------------------------- |
8 | 8 |
|
9 | 9 | Here are the topics that have been cooking. Commits prefixed with '-' are |
10 | 10 | only in 'pu' while commits prefixed with '+' are in 'next'. The ones |
11 | 11 | marked with '.' do not appear in any of the integration branches, but I am |
12 | 12 | still holding onto them. |
13 | 13 |
|
14 | | -We are passed 1.7.0-rc1; please test "master" branch to avoid giving |
15 | | -regressions to end users. Thanks. |
| 14 | +There shouldn't be anything exciting to see here right now. Please test |
| 15 | +"master" branch to avoid giving regressions to end users; we are at |
| 16 | +1.7.0-rc2 and I am hoping that we can release the 1.7.0 on the 10th. |
16 | 17 |
|
17 | 18 | -------------------------------------------------- |
18 | | -[Graduated to "master"] |
| 19 | +[New Topics] |
19 | 20 |
|
20 | | -* bw/no-python-autoconf (2010-01-31) 2 commits |
21 | | - (merged to 'next' on 2010-02-01 at 7c70402) |
22 | | - + configure: Allow --without-python |
23 | | - + configure: Allow GIT_ARG_SET_PATH to handle --without-PROGRAM |
| 21 | +* sp/maint-push-sideband (2010-02-05) 6 commits |
| 22 | + - receive-pack: Send hook output over side band #2 |
| 23 | + - receive-pack: Wrap status reports inside side-band-64k |
| 24 | + - receive-pack: Refactor how capabilities are shown to the client |
| 25 | + - send-pack: demultiplex a sideband stream with status data |
| 26 | + - run-command: support custom fd-set in async |
| 27 | + - run-command: Allow stderr to be a caller supplied pipe |
| 28 | + (this branch is used by sp/push-sideband.) |
24 | 29 |
|
25 | | -* ms/filter-branch-submodule (2010-01-28) 2 commits |
26 | | - (merged to 'next' on 2010-01-28 at 226cbf8) |
27 | | - + filter-branch: Add tests for submodules in tree-filter |
28 | | - + filter-branch: Fix to allow replacing submodules with another content |
| 30 | +Based on 1.6.5 maintenance track |
29 | 31 |
|
30 | | -* sp/maint-fast-import-large-blob (2010-02-01) 1 commit |
31 | | - (merged to 'next' on 2010-02-01 at 04d206f) |
32 | | - + fast-import: Stream very large blobs directly to pack |
33 | | - (this branch is used by sp/fast-import-large-blob.) |
| 32 | +* sp/push-sideband (2010-02-05) 0 commits |
| 33 | + (this branch uses sp/maint-push-sideband.) |
34 | 34 |
|
35 | | -Importing a large blob via fast-import may bust the pack size limit (or |
36 | | -2GB filesize limit found on some filesystems). |
| 35 | +And my conflict resolution in #ifdef WINDOWS codepath (meaning: untested, |
| 36 | +please check). |
37 | 37 |
|
38 | | -* sp/fast-import-large-blob (2010-02-01) 0 commits |
39 | | - (this branch uses sp/maint-fast-import-large-blob.) |
| 38 | +* ac/cvsimport-revision-mapping (2010-02-06) 1 commit |
| 39 | + - cvsimport: new -R option: generate .git/cvs-revisions mapping |
40 | 40 |
|
41 | | -And this is to help merging the topic to newer codebase. |
| 41 | +* jc/maint-1.6.3-imap-send-bool-config-fix (2010-02-06) 1 commit |
| 42 | + - imap-send: fix longstanding configuration parser bug |
42 | 43 |
|
43 | | --------------------------------------------------- |
44 | | -[New Topics] |
| 44 | +* js/rebase-origin-x (2010-02-05) 1 commit |
| 45 | + - [RFC w/o test and incomplete] rebase: add -x option to record original commit name |
| 46 | + |
| 47 | +* rs/git-dir-cleanup (2010-02-06) 2 commits |
| 48 | + (merged to 'next' on 2010-02-06 at ef8ab9b) |
| 49 | + + Resurrect "git grep --no-index" |
| 50 | + + setenv(GIT_DIR) clean-up |
45 | 51 |
|
46 | 52 | * jc/typo (2010-02-03) 1 commit |
47 | 53 | - Typofixes outside documentation area |
48 | 54 |
|
| 55 | +* jk/grep-double-dash (2010-02-06) 1 commit |
| 56 | + (merged to 'next' on 2010-02-07 at 2ac040d) |
| 57 | + + accept "git grep -- pattern" |
| 58 | + |
49 | 59 | -------------------------------------------------- |
50 | 60 | [Cooking] |
51 | 61 |
|
@@ -104,12 +114,6 @@ of 'master' until 1.7.0 ships. |
104 | 114 | - reset: add test cases for "--keep" option |
105 | 115 | - reset: add option "--keep" to "git reset" |
106 | 116 |
|
107 | | -I do not think I'd ever use this, and I am not convinced I can sell this |
108 | | -to users as a great new feature without confusing them unnecessarily, but |
109 | | -perhaps queuing it to pu to give it wider visibility may help somebody |
110 | | -coming up with a better way to defend the feature and introduce it to |
111 | | -users without confusing them than Christan nor I managed to. |
112 | | - |
113 | 117 | * jh/notes (2010-01-27) 23 commits |
114 | 118 | - builtin-notes: Add "add" subcommand for appending to note objects |
115 | 119 | - builtin-notes: Add "list" subcommand for listing note objects |
|
0 commit comments