{"thread":{"id":"33963","subject":"What's cooking in git.git (May 2013, #08; Tue, 28)","startedAt":"2013-05-28T21:54:00Z","lastAt":"2013-05-29T23:44:52Z","messageCount":12,"participants":["Junio C Hamano","Felipe Contreras","Ramkumar Ramachandra","Matthieu Moy","Ramsay Jones"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"218702","messageId":"7vli6yydmv.fsf@alter.siamese.dyndns.org","threadId":"33963","inReplyTo":null,"subject":"What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-05-28T21:54:00Z","receivedAt":"2013-05-28T21:54:00Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here are the topics that have been cooking.  Commits prefixed with\n'-' are only in 'pu' (proposed updates) while commits prefixed with\n'+' are in 'next'.\n\nThere are topics that are still in 'next', not because they needed\nmore testing, but only because we already were in the -rc period.\nNow that 1.8.3 is out, we will start merging them to 'master' (and\nsome to 'maint' for 1.8.3.1) probably tomorrow (i.e. after waiting\nfor a few days to make sure we can have a clean start of the post\n1.8.3 maint branch with brown paper bag fixes and nothing else).\n\nThe post 1.8.3 cycle will start early next month, at which time the\n'next' branch will be rewound and rebuilt.  Until then, I expect\nthat my patch queue may stay slow and leaky while I take a bit of\nbreak.\n\nYou can find the changes described here in the integration branches\nof the repositories listed at\n\n    http://git-blame.blogspot.com/p/git-public-repositories.html\n\n--------------------------------------------------\n[New Topics]\n\n* nd/urls-doc-no-file-hyperlink-fix (2013-05-24) 1 commit\n - urls.txt: avoid auto converting to hyperlink\n\n Will merge to 'next'.\n\n\n* cb/log-follow-with-combined (2013-05-28) 1 commit\n - fix segfault with git log -c --follow\n\n Will merge to 'next'.\n\n\n* fc/cleanups (2013-05-28) 3 commits\n - test: rebase: fix --interactive test\n - test: trivial cleanups\n - remote: trivial style cleanup\n\n Will merge to 'next'.\n\n\n* fc/makefile (2013-05-26) 5 commits\n - build: do not install git-remote-testpy\n - build: add NO_INSTALL variable\n - build: cleanup using $<\n - build: cleanup using $^\n - build: trivial simplification\n (this branch is used by fc/remote-helpers-use-specified-python.)\n\n Will merge to 'next'.\n\n\n* fc/remote-helpers-use-specified-python (2013-05-28) 4 commits\n - remote-helpers: add exec-path links\n - remote-helpers: allow direct test execution\n - remote-helpers: rename tests\n - remote-helpers: generate scripts\n (this branch uses fc/makefile.)\n\n I do not particularly think the second from the bottom is a good\n change, but it takes the remainder of the series hostage.\n Will hopefully be rerolled without it.\n\n\n* fc/send-email-chainreplyto-warning (2013-05-28) 1 commit\n - send-email: remove warning about unset chainreplyto\n\n An overdue removal od \"behaviour changed at 1.7.0; if you were\n living in a cave, here is what you can adjust to it\" message.\n\n Will merge to 'next'.\n\n\n* ks/difftool-dirdiff-copy-all (2013-05-28) 1 commit\n - difftool --dir-diff: always use identical working tree file\n\n \"difftool --dir-diff\" populates a temporary directory with files,\n inviting the user to modify them in place, but in some cases we\n weren't expecting the user to modify them and did not take the\n change back to the working tree.\n\n The log message has room for clarification, but the change looked\n sane.\n\n\n* nd/prune-packed-dryrun-verbose (2013-05-28) 1 commit\n - prune-packed: avoid implying \"1\" is DRY_RUN in prune_packed_objects()\n\n Will merge to 'next'.\n\n\n* rj/mingw-compat-st-mode-bits (2013-05-28) 1 commit\n - path: Fix a sparse warning\n\n Will merge to 'next'.\n\n\n* rs/commit-m-no-edit (2013-05-28) 1 commit\n - commit: don't start editor if empty message is given with -m\n\n Will merge to 'next'.\n\n\n* xq/credential-osxkeychain (2013-05-28) 1 commit\n - credential-osxkeychain: support more protocols\n\n Will merge to 'next'.\n\n\n* jc/core-checkstat (2013-05-06) 1 commit\n - deprecate core.statinfo at Git 2.0 boundary\n (this branch is used by jc/core-checkstat-2.0.)\n\n Will merge to 'next'.\n\n--------------------------------------------------\n[Stalled]\n\n* rr/rebase-autostash (2013-05-12) 7 commits\n - rebase: implement --[no-]autostash and rebase.autostash\n - rebase --merge: return control to caller, for housekeeping\n - rebase -i: return control to caller, for housekeeping\n - am: return control to caller, for housekeeping\n - rebase: prepare to do generic housekeeping\n - rebase -i: don't error out if $state_dir already exists\n - am: tighten a conditional that checks for $dotest\n\n This is from v3, but after a \"Fixed\" message in $gmane/224111 we\n haven't seen a reroll yet.  Also there was an attempt for a\n follow-up, but it was never completed.\n\n\n* rj/mingw-cygwin (2013-05-08) 2 commits\n - cygwin: Remove the CYGWIN_V15_WIN32API build variable\n - mingw: rename WIN32 cpp macro to GIT_WINDOWS_NATIVE\n\n Update build for Cygwin 1.[57].  There seems to have been some\n discussion but did anything concrete come out of it???\n\n\n* mh/multimail (2013-04-21) 1 commit\n - git-multimail: a replacement for post-receive-email\n\n Waiting for the initial history to pull from.\n $gmane/223564\n\n\n* jc/format-patch (2013-04-22) 2 commits\n - format-patch: --inline-single\n - format-patch: rename \"no_inline\" field\n\n A new option to send a single patch to the standard output to be\n appended at the bottom of a message.  I personally have no need for\n this, but it was easy enough to cobble together.  Tests, docs and\n stripping out more MIMEy stuff are left as exercises to interested\n parties.\n\n Not ready for inclusion.\n\n\n* jk/gitweb-utf8 (2013-04-08) 4 commits\n - gitweb: Fix broken blob action parameters on blob/commitdiff pages\n - gitweb: Don't append ';js=(0|1)' to external links\n - gitweb: Make feed title valid utf8\n - gitweb: Fix utf8 encoding for blob_plain, blobdiff_plain, commitdiff_plain, and patch\n\n Various fixes to gitweb.\n\n Waiting for a reroll after a review.\n\n\n* jk/commit-info-slab (2013-04-19) 3 commits\n - commit-slab: introduce a macro to define a slab for new type\n - commit-slab: avoid large realloc\n - commit: allow associating auxiliary info on-demand\n (this branch is used by jc/show-branch.)\n\n Technology demonstration to show a way we could use unbound number\n of flag bits on commit objects.\n\n--------------------------------------------------\n[Cooking]\n\n* tr/line-log (2013-04-22) 13 commits\n  (merged to 'next' on 2013-04-22 at 8f2c1de)\n + git-log(1): remove --full-line-diff description\n  (merged to 'next' on 2013-04-21 at cd92620)\n + line-log: fix documentation formatting\n  (merged to 'next' on 2013-04-15 at 504559e)\n + log -L: improve comments in process_all_files()\n + log -L: store the path instead of a diff_filespec\n + log -L: test merge of parallel modify/rename\n + t4211: pass -M to 'git log -M -L...' test\n  (merged to 'next' on 2013-04-05 at 5afb00c)\n + log -L: fix overlapping input ranges\n + log -L: check range set invariants when we look it up\n  (merged to 'next' on 2013-04-01 at 5be920c)\n + Speed up log -L... -M\n + log -L: :pattern:file syntax to find by funcname\n + Implement line-history search (git log -L)\n + Export rewrite_parents() for 'log -L'\n + Refactor parse_loc\n\n Will merge to 'master'.\n\n\n* jn/config-ignore-inaccessible (2013-04-15) 1 commit\n  (merged to 'next' on 2013-05-07 at 4f09e24)\n + config: allow inaccessible configuration under $HOME\n\n When $HOME is misconfigured to point at an unreadable directory, we\n used to complain and die. This loosens the check.\n\n Will merge to 'master'.\n\n\n* mh/reflife (2013-05-28) 25 commits\n - refs: document the lifetime of the args passed to each_ref_fn\n - register_ref(): make a copy of the bad reference SHA-1\n - exclude_existing(): set existing_refs.strdup_strings\n - string_list_add_refs_by_glob(): add a comment about memory management\n - string_list_add_one_ref(): rename first parameter to \"refname\"\n - show_head_ref(): rename first parameter to \"refname\"\n - show_head_ref(): do not shadow name of argument\n - add_existing(): do not retain a reference to sha1\n - do_fetch(): clean up existing_refs before exiting\n - do_fetch(): reduce scope of peer_item\n - object_array_entry: fix memory handling of the name field\n - find_first_merges(): remove unnecessary code\n - find_first_merges(): initialize merges variable using initializer\n - fsck: don't put a void*-shaped peg in a char*-shaped hole\n - object_array_remove_duplicates(): rewrite to reduce copying\n - revision: use object_array_filter() in implementation of gc_boundary()\n - object_array: add function object_array_filter()\n - revision: split some overly-long lines\n - cmd_diff(): make it obvious which cases are exclusive of each other\n - cmd_diff(): rename local variable \"list\" -> \"entry\"\n - cmd_diff(): use an object_array for holding trees\n - builtin_diff_tree(): make it obvious that function wants two entries\n - add_rev_cmdline(): make a copy of the name argument\n - fetch: make own copies of refnames\n - describe: make own copy of refname\n\n Define memory ownership and lifetime rules for what for-each-ref\n feeds to its callbacks (in short, \"you do not own it, so make a\n copy if you want to keep it\").\n\n\n* th/bisect-skip-report-range-fix (2013-05-22) 1 commit\n - bisect: Fix log output for multi-parent skip ranges\n\n Fix for an additional bisect log comments.\n\n Will merge to 'next'.\n\n\n* mm/mediawiki-https-fail-message (2013-05-23) 1 commit\n - git-remote-mediawiki: better error message when HTTP(S) access fails\n\n Hint users when https:// connection failed to check the\n certificate; it is a good hint if we assumie that it is common\n error for the end users to make.\n\n Still under discussion.\n $gmane/225678\n\n\n* tg/maint-zsh-svn-remote-prompt (2013-05-22) 1 commit\n - prompt: fix show upstream with svn and zsh\n\n zsh prompt script that borrowed from bash prompt script did not\n work due to slight differences in array variable notation between\n these two shells.\n\n Will merge to 'next'.\n\n\n* tr/push-no-verify-doc (2013-05-23) 1 commit\n - Document push --no-verify\n\n \"git push --[no-]verify\" was not documented.\n\n Will merge to 'next'.\n\n\n* dm/unbash-subtree (2013-05-21) 1 commit\n - contrib/git-subtree: Use /bin/sh interpreter instead of /bin/bash\n\n It turns out that git-subtree script does not have to be run with\n bash.\n\n Will merge to 'next'.\n\n\n* fc/transport-helper-no-refspec (2013-05-21) 2 commits\n - transport-helper: check if the dry-run is supported\n - transport-helper: barf when user tries old:new\n\n With \"export\" remote-helper protocol, (1) a push that tries to\n update a remote ref whose name is different from the pushing side\n does not work yet, and (2) the helper may not know how to do\n --dry-run, so detect such problematic cases and disable them for\n now.\n\n Will merge to 'next'.\n\n\n* rr/die-on-missing-upstream (2013-05-22) 2 commits\n - sha1_name: fix error message for @{<N>}, @{<date>}\n - sha1_name: fix error message for @{u}\n\n When a reflog notation is used for implicit \"current branch\", we\n did not say which branch and worse said \"branch ''\".\n\n Waiting for series of rerolls to settle.\n\n\n* jc/show-branch (2013-05-21) 5 commits\n - show-branch: use commit slab to represent bitflags of arbitrary width\n - show-branch.c: remove \"all_mask\"\n - show-branch.c: abstract out \"flags\" operation\n - show-branch.c: lift all_mask/all_revs to a global static\n - show-branch.c: update comment style\n (this branch uses jk/commit-info-slab.)\n\n Waiting for the final step to lift the hard-limit before sending it out.\n\n\n* fc/remote-bzr (2013-05-28) 8 commits\n - remote-bzr: add fallback check for a partial clone\n - remote-bzr: reorganize the way 'wanted' works\n - remote-bzr: trivial cleanups\n - remote-bzr: change global repo\n - remote-bzr: delay cloning/pulling\n - remote-bzr: simplify get_remote_branch()\n - remote-bzr: fix for files with spaces\n - remote-bzr: recover from failed clones\n\n The ones near the tip conflicted with the hotfix for 1.8.3 so I\n discarded them for now.\n\n Will merge to 'next'?\n\n\n* jx/clean-interactive (2013-05-22) 15 commits\n - test: add t7301 for git-clean--interactive\n - git-clean: add documentation for interactive git-clean\n - git-clean: add ask each interactive action\n - git-clean: add select by numbers interactive action\n - git-clean: add filter by pattern interactive action\n - git-clean: use a git-add-interactive compatible UI\n - git-clean: add colors to interactive git-clean\n - git-clean: show items of del_list in columns\n - git-clean: add support for -i/--interactive\n - git-clean: refactor git-clean into two phases\n - Refactor write_name_quoted_relative, remove unused params\n - Refactor quote_path_relative, remove unused params\n - quote.c: remove path_relative, use relative_path instead\n - path.c: refactor relative_path(), not only strip prefix\n - test: add test cases for relative_path\n\n Still under discussion, e.g. $gmane/225139.\n\n\n* tr/test-v-and-v-subtest-only (2013-05-16) 6 commits\n - test-lib: support running tests under valgrind in parallel\n - test-lib: allow prefixing a custom string before \"ok N\" etc.\n - test-lib: valgrind for only tests matching a pattern\n - test-lib: verbose mode for only tests matching a pattern\n - test-lib: refactor $GIT_SKIP_TESTS matching\n - test-lib: enable MALLOC_* for the actual tests\n\n Allows N instances of tests run in parallel, each running 1/N parts\n of the test suite under Valgrind, to speed things up.\n\n The tip one may be useful in practice but is a tad ugly ;-)\n Will merge to 'next'.\n\n\n* rh/merge-options-doc-fix (2013-05-16) 1 commit\n  (merged to 'next' on 2013-05-21 at f76baf3)\n + Documentation/merge-options.txt: restore `-e` option\n\n Will merge to 'master'.\n\n\n* rr/zsh-color-prompt (2013-05-17) 3 commits\n - prompt: colorize ZSH prompt\n - prompt: factor out gitstring coloring logic\n - prompt: introduce GIT_PS1_STATESEPARATOR\n\n Will merge to 'next'.\n\n\n* an/diff-index-doc (2013-05-20) 1 commit\n  (merged to 'next' on 2013-05-21 at 6e1459b)\n + Documentation/diff-index: mention two modes of operation\n\n Will merge to 'master'.\n\n\n* fc/contrib-related (2013-05-20) 1 commit\n - Add new git-related helper to contrib\n\n Waiting the design review for this earliest part to settle.\n\n\n* mc/describe-first-parent (2013-05-20) 1 commit\n  (merged to 'next' on 2013-05-21 at 2e02ffc)\n + describe: Add --first-parent option\n\n Will merge to 'master'.\n\n\n* rs/tar-tests (2013-05-20) 6 commits\n  (merged to 'next' on 2013-05-21 at aed12a7)\n + t5000: test long filenames\n + t5000: simplify tar-tree tests\n + t5000: use check_tar for prefix test\n + t5000: factor out check_tar\n + t5000, t5003: create directories for extracted files lazily\n + t5000: integrate export-subst tests into regular tests\n\n Will merge to 'master'.\n\n\n* da/darwin (2013-05-21) 4 commits\n  (merged to 'next' on 2013-05-21 at 0497edb)\n + imap-send: eliminate HMAC deprecation warnings on Mac OS X\n + cache.h: eliminate SHA-1 deprecation warnings on Mac OS X\n + Makefile: add support for Apple CommonCrypto facility\n + Makefile: fix default regex settings on Darwin\n\n Newer MacOS X encourages the programs to compile and link with\n their CommonCrypto, not with OpenSSL.\n\n Will merge to 'master'.\n\n\n* fc/macos-x-clipped-write (2013-05-17) 1 commit\n  (merged to 'next' on 2013-05-21 at 510b0dd)\n + compate/clipped-write.c: large write(2) fails on Mac OS X/XNU\n\n Mac OS X does not like to write(2) more than INT_MAX number of\n bytes.\n\n Will merge to 'master'.\n\n\n* fc/remote-hg (2013-05-28) 50 commits\n - remote-hg: add support for --force\n - remote-hg: add support for --dry-run\n - remote-hg: check if a fetch is needed\n - remote-hg: trivial cleanup\n - remote-helpers: improve marks usage\n - remote-hg: add check_push() helper\n - remote-hg: add setup_big_push() helper\n - remote-hg: remove files before modifications\n - remote-hg: improve lightweight tag author\n - remote-hg: use remote 'default' not local one\n - remote-hg: improve branch listing\n - remote-hg: simplify branch_tip()\n - remote-hg: check diverged bookmarks\n - remote-hg: pass around revision refs\n - remote-hg: implement custom checkheads()\n - remote-hg: implement custom push()\n - remote-hg: only update necessary revisions\n - remote-hg: force remote bookmark push selectively\n - remote-hg: reorganize bookmark handling\n - remote-hg: add test for failed double push\n - remote-hg: add test for big push\n - remote-hg: add test for new bookmark special\n - remote-hg: add test for bookmark diverge\n - remote-hg: add test for diverged push\n - remote-hg: add test to push new bookmark\n - remote-hg: add remote tests\n - remote-hg: update bookmarks when using a remote\n - remote-hg: add check_bookmark() test helper\n - remote-bzr: simplify test checks\n - remote-hg: add tests for 'master' bookmark\n - remote-hg: always point HEAD to master\n - remote-hg: improve progress calculation\n - remote-hg: trivial cleanups\n - remote-hg: ensure remote rebasing works\n - remote-hg: upgrade version 1 marks\n - remote-hg: switch from revisions to SHA-1 noteids\n - remote-hg: add version checks to the marks\n - remote-hg: improve node traversing\n - remote-hg: shuffle some code\n - remote-hg: use a shared repository store\n - remote-hg: load all extensions\n - remote-hg: test: simplify previous branch checkout\n - remote-helpers: test: simplify remote URLs\n - remote-helpers: tests: general improvements\n - remote-helpers: test: cleanup style\n - remote-helpers: test: cleanup white-spaces\n - remote-hg: trivial reorganization\n - remote-hg: test: be a little more quiet\n - remote-hg: tests: fix hg merge\n - remote-helpers: tests: use python directly\n\n Will merge to 'next'.\n\n\n* hv/config-from-blob (2013-05-12) 5 commits\n - do not die when error in config parsing of buf occurs\n - teach config --blob option to parse config from database\n - config: make parsing stack struct independent from actual data source\n - config: drop cf validity check in get_next_char()\n - config: factor out config file stack management\n\n Will see a resubmit.\n $gmane/223964\n\n\n* jc/t5551-posix-sed-bre (2013-05-12) 1 commit\n  (merged to 'next' on 2013-05-21 at d597ca1)\n + t5551: do not use unportable sed '\\+'\n\n POSIX fix for a test script.\n\n Will merge to 'master'.\n\n\n* jk/fetch-always-update-tracking (2013-05-28) 5 commits\n  (merged to 'next' on 2013-05-28 at c6abf3f)\n + fetch: don't try to update unfetched tracking refs\n  (merged to 'next' on 2013-05-21 at f7e4b16)\n + fetch: opportunistically update tracking refs\n + refactor \"ref->merge\" flag\n + fetch/pull doc: untangle meaning of bare <ref>\n + t5510: start tracking-ref tests from a known state\n\n \"git fetch origin master\" unlike \"git fetch origin\" or \"git fetch\"\n does not update \"refs/remotes/origin/master\" and it was an early\n design decision to keep the update of remote tracking branches\n predictable, but in practice it turns out that people find it more\n convenient to opportunisticly update them whenever we have a\n chance, and we have been updating them when we run \"git push\" which\n already breaks the original \"predictability\" anyway.\n\n Will merge to 'master'.\n\n\n* nd/clone-connectivity-shortcut (2013-05-28) 4 commits\n - clone: open a shortcut for connectivity check\n - index-pack: remove dead code (it should never happen)\n - fetch-pack: prepare updated shallow file before fetching the pack\n - clone: let the user know when check_everything_connected is run\n\n Will merge to 'next'.\n\n\n* kb/ancestry-path-threedots (2013-05-16) 2 commits\n  (merged to 'next' on 2013-05-21 at 5d75bd3)\n + revision.c: treat A...B merge bases as if manually specified\n + t6019: demonstrate --ancestry-path A...B breakage\n (this branch is used by kb/full-history-compute-treesame-carefully-2.)\n\n \"git log --ancestry-path A...B\" did not work as expected, as it did\n not pay attention to the fact that the merge base between A and B\n was the bottom of the range being specified.\n\n Will merge to 'master'.\n\n\n* kb/full-history-compute-treesame-carefully-2 (2013-05-16) 15 commits\n - revision.c: make default history consider bottom commits\n - revision.c: don't show all merges for --parents\n - revision.c: discount side branches when computing TREESAME\n - revision.c: add BOTTOM flag for commits\n - simplify-merges: drop merge from irrelevant side branch\n - simplify-merges: never remove all TREESAME parents\n - t6012: update test for tweaked full-history traversal\n - revision.c: Make --full-history consider more merges\n - Documentation: avoid \"uninteresting\"\n - rev-list-options.txt: correct TREESAME for P\n - t6111: add parents to tests\n - t6111: allow checking the parents as well\n - t6111: new TREESAME test set\n - t6019: test file dropped in -s ours merge\n - decorate.c: compact table when growing\n (this branch uses kb/ancestry-path-threedots.)\n\n Major update to a very core part of the system to improve culling\n of irrelevant parents while traversing a mergy history.\n\n Will not be a 1.8.3 material, but is an important topic.\n\n Will merge to 'next'.\n\n\n* jc/strbuf-branchname-fix (2013-05-16) 1 commit\n  (merged to 'next' on 2013-05-21 at 5db8872)\n + strbuf_branchname(): do not double-expand @{-1}~22\n\n \"git merge @{-1}~22\" was rewritten to \"git merge frotz@{1}~22\"\n incorrectly when your previous branch was \"frotz\" (it should be\n rewritten to \"git merge frotz~22\" instead).\n\n Will merge to 'master'.\n\n\n* mk/combine-diff-context-horizon-fix (2013-05-15) 1 commit\n  (merged to 'next' on 2013-05-21 at f462c02)\n + combine-diff.c: Fix output when changes are exactly 3 lines apart\n\n \"git diff -c -p\" was not showing a deleted line from a hunk when\n another hunk immediately begins where the earlier one ends.\n\n Will merge to 'master'.\n\n\n* mm/color-auto-default (2013-05-15) 2 commits\n - make color.ui default to 'auto'\n - config: refactor management of color.ui's default value\n\n Flip the default for color.ui to 'auto', which is what many\n tutorials recommend new users to do.  The updated code claims the\n switch happened at Git 2.0 in the past tense, but we might want to\n expedite it, as this change is not all that important to deserve a\n major version bump.\n\n I'd vote for merging this without waiting for 2.0.  Comments?\n Waiting for a reroll.\n\n\n* tr/coverage (2013-05-13) 4 commits\n  (merged to 'next' on 2013-05-21 at 8480007)\n + coverage: build coverage-untested-functions by default\n + coverage: set DEFAULT_TEST_TARGET to avoid using prove\n + coverage: do not delete .gcno files before building\n + coverage: split build target into compile and test\n\n Update the test coverage support that was left to bitrot for some\n time.\n\n Will merge to 'master'.\n\n\n* mg/more-textconv (2013-05-10) 7 commits\n  (merged to 'next' on 2013-05-21 at 701cdb7)\n + grep: honor --textconv for the case rev:path\n + grep: allow to use textconv filters\n + t7008: demonstrate behavior of grep with textconv\n + cat-file: do not die on --textconv without textconv filters\n + show: honor --textconv for blobs\n + diff_opt: track whether flags have been set explicitly\n + t4030: demonstrate behavior of show with textconv\n\n Make \"git grep\" and \"git show\" pay attention to --textconv when\n dealing with blob objects.\n\n I thought this was pretty well designed and executed, but it seems\n there are some doubts on the list.\n\n\n* jh/shorten-refname (2013-05-07) 4 commits\n - t1514: refname shortening is done after dereferencing symbolic refs\n - shorten_unambiguous_ref(): Fix shortening refs/remotes/origin/HEAD to origin\n - t1514: Demonstrate failure to correctly shorten \"refs/remotes/origin/HEAD\"\n - t1514: Add tests of shortening refnames in strict/loose mode\n\n When remotes/origin/HEAD is not a symbolic ref, \"rev-parse\n --abbrev-ref remotes/origin/HEAD\" ought to show \"origin\", not\n \"origin/HEAD\", which is fixed with this series (if it is a symbolic\n ref that points at remotes/origin/something, then it should show\n \"origin/something\" and it already does).\n\n Expecting a reroll, as an early part of a larger series.\n\n\n* nd/clone-local-with-colon (2013-05-07) 1 commit\n  (merged to 'next' on 2013-05-21 at 3e293bd)\n + clone: allow cloning local paths with colons in them\n\n \"git clone foo/bar:baz\" cannot be a request to clone from a remote\n over git-over-ssh specified in the scp style.  Detect this case and\n clone from a local repository at \"foo/bar:baz\".\n\n Will merge to 'master'.\n\n\n* nd/warn-ambiguous-object-name (2013-05-07) 1 commit\n - get_sha1: improve ambiguity warning regarding SHA-1 and ref names\n\n \"git cmd <name>\", when <name> happens to be a 40-hex string,\n directly uses the 40-hex string as an object name, even if a ref\n \"refs/<some hierarchy>/<name>\" exists.  This disambiguation order\n is unlikely to change, but we should warn about the ambiguity just\n like we warn when more than one refs/ hierachies share the same\n name.\n\n Will be rerolled.\n $gmane/225585\n\n\n* fc/zsh-leftover-bits (2013-05-28) 3 commits\n  (merged to 'next' on 2013-05-28 at d4a7aee)\n + completion: zsh: improve bash script loading\n  (merged to 'next' on 2013-05-21 at 1b84ec1)\n + completion: synchronize zsh wrapper\n + completion: cleanup zsh wrapper\n\n Will merge to 'master'.\n\n\n* rs/empty-archive (2013-05-09) 2 commits\n  (merged to 'next' on 2013-05-21 at 3e9e288)\n + t5004: resurrect original empty tar archive test\n + t5004: avoid using tar for checking emptiness of archive\n\n Fixes tests added in 1.8.2 era that are broken on BSDs.\n\n Will merge to 'master'.\n\n\n* vv/help-unknown-ref (2013-05-08) 2 commits\n  (merged to 'next' on 2013-05-21 at 77a2941)\n + merge: use help_unknown_ref()\n + help: add help_unknown_ref()\n\n Detect \"git merge foo\" that might have meant \"git merge origin/foo\"\n and give an error message that is more specific than \"foo is not\n something we can merge\".\n\n Will merge to 'master'.\n\n\n* fc/fast-export-persistent-marks (2013-05-07) 3 commits\n  (merged to 'next' on 2013-05-21 at 10b8214)\n + fast-{import,export}: use get_sha1_hex() to read from marks file\n + fast-export: don't parse commits while reading marks file\n + fast-export: do not parse non-commit objects while reading marks file\n\n Optimization for fast-export by avoiding unnecessarily resolving\n arbitrary object name and parsing object when only presence and\n type information is necessary, etc.\n\n Will merge to 'master'.\n\n\n* jk/packed-refs-race (2013-05-06) 4 commits\n - for_each_ref: load all loose refs before packed refs\n - get_packed_refs: reload packed-refs file when it changes\n - add a stat_validity struct\n - resolve_ref: close race condition for packed refs\n\n What is the status of this thing?\n\n\n* fc/at-head (2013-05-08) 13 commits\n - sha1_name: compare variable with constant, not constant with variable\n - Add new @ shortcut for HEAD\n - sha1_name: refactor reinterpret()\n - sha1_name: check @{-N} errors sooner\n - sha1_name: reorganize get_sha1_basic()\n - sha1_name: don't waste cycles in the @-parsing loop\n - sha1_name: remove unnecessary braces\n - sha1_name: remove no-op\n - tests: at-combinations: @{N} versus HEAD@{N}\n - tests: at-combinations: increase coverage\n - tests: at-combinations: improve nonsense()\n - tests: at-combinations: check ref names directly\n - tests: at-combinations: simplify setup\n\n Instead of typing four capital letters \"HEAD\", you can say \"@\"\n instead.\n\n Will merge to 'next'.\n\n\n* jk/lookup-object-prefer-latest (2013-05-02) 1 commit\n  (merged to 'next' on 2013-05-06 at cc59dcc)\n + lookup_object: prioritize recently found objects\n\n Optimizes object lookup when the object hashtable starts to become\n crowded.\n\n Will merge to 'master'.\n\n\n* jk/subtree-do-not-push-if-split-fails (2013-05-01) 1 commit\n  (merged to 'next' on 2013-05-06 at 81bdf37)\n + contrib/subtree: don't delete remote branches if split fails\n\n \"git subtree\" (in contrib/) had one codepath with loose error\n checks to lose data at the remote side.\n\n Will merge to 'master'.\n\n\n* fc/completion (2013-04-27) 9 commits\n  (merged to 'next' on 2013-05-21 at aba6ef1)\n + completion: remove __git_index_file_list_filter()\n + completion: add space after completed filename\n + completion: add hack to enable file mode in bash < 4\n + completion: refactor __git_complete_index_file()\n + completion: refactor diff_index wrappers\n + completion: use __gitcompadd for __gitcomp_file\n + completion; remove unuseful comments\n + completion: document tilde expansion failure in tests\n + completion: add file completion tests\n\n Will merge to 'master'.\n\n\n* jk/test-output (2013-05-06) 3 commits\n  (merged to 'next' on 2013-05-06 at 7c03af3)\n + t/Makefile: don't define TEST_RESULTS_DIRECTORY recursively\n  (merged to 'next' on 2013-05-01 at 63827c9)\n + test output: respect $TEST_OUTPUT_DIRECTORY\n + t/Makefile: fix result handling with TEST_OUTPUT_DIRECTORY\n\n When TEST_OUTPUT_DIRECTORY setting is used, it was handled somewhat\n inconsistently between the test framework and t/Makefile, and logic\n to summarize the results looked at a wrong place.\n\n Will merge to 'master'.\n\n\n* rj/sparse (2013-04-28) 10 commits\n  (merged to 'next' on 2013-05-01 at 649e16c)\n + sparse: Fix mingw_main() argument number/type errors\n + compat/mingw.c: Fix some sparse warnings\n + compat/win32mmap.c: Fix some sparse warnings\n + compat/poll/poll.c: Fix a sparse warning\n + compat/win32/pthread.c: Fix a sparse warning\n + compat/unsetenv.c: Fix a sparse warning\n + compat/nedmalloc: Fix compiler warnings on linux\n + compat/nedmalloc: Fix some sparse warnings\n + compat/fnmatch/fnmatch.c: Fix a sparse error\n + compat/regex/regexec.c: Fix some sparse warnings\n\n Will merge to 'master'.\n\n\n* mh/fetch-into-shallow (2013-05-02) 2 commits\n  (merged to 'next' on 2013-05-03 at 3fadc61)\n + t5500: add test for fetching with an unknown 'shallow'\n  (merged to 'next' on 2013-04-29 at a167d3e)\n + upload-pack: ignore 'shallow' lines with unknown obj-ids\n\n Will merge to 'master'.\n\n\n* jh/checkout-auto-tracking (2013-04-21) 8 commits\n  (merged to 'next' on 2013-04-22 at 2356700)\n + glossary: Update and rephrase the definition of a remote-tracking branch\n + branch.c: Validate tracking branches with refspecs instead of refs/remotes/*\n + t9114.2: Don't use --track option against \"svn-remote\"-tracking branches\n + t7201.24: Add refspec to keep --track working\n + t3200.39: tracking setup should fail if there is no matching refspec.\n + checkout: Use remote refspecs when DWIMming tracking branches\n + t2024: Show failure to use refspec when DWIMming remote branch names\n + t2024: Add tests verifying current DWIM behavior of 'git checkout <branch>'\n\n Updates \"git checkout foo\" that DWIMs the intended \"upstream\" and\n turns it into \"git checkout -t -b foo remotes/origin/foo\" to\n correctly take existing remote definitions into account.  The\n remote \"origin\" may be what uniquely map its own branch to\n remotes/some/where/foo but that some/where may not be \"origin\".\n\n Will merge to 'master'.\n\n\n* jc/prune-all (2013-04-25) 4 commits\n  (merged to 'next' on 2013-04-26 at 97a7387)\n + prune: introduce OPT_EXPIRY_DATE() and use it\n  (merged to 'next' on 2013-04-22 at b00ccf6)\n + api-parse-options.txt: document \"no-\" for non-boolean options\n + git-gc.txt, git-reflog.txt: document new expiry options\n + date.c: add parse_expiry_date()\n (this branch is used by mh/packed-refs-various.)\n\n We used the approxidate() parser for \"--expire=<timestamp>\" options\n of various commands, but it is better to treat --expire=all and\n --expire=now a bit more specially than using the current timestamp.\n Update \"git gc\" and \"git reflog\" with a new parsing function for\n expiry dates.\n\n Will merge to 'master'.\n\n\n* as/check-ignore (2013-04-29) 6 commits\n  (merged to 'next' on 2013-04-30 at 646931f)\n + t0008: use named pipe (FIFO) to test check-ignore streaming\n  (merged to 'next' on 2013-04-21 at 7515aa8)\n + Documentation: add caveats about I/O buffering for check-{attr,ignore}\n + check-ignore: allow incremental streaming of queries via --stdin\n + check-ignore: move setup into cmd_check_ignore()\n + check-ignore: add -n / --non-matching option\n + t0008: remove duplicated test fixture data\n\n Enhance \"check-ignore\" (1.8.2 update) to work more like \"check-attr\"\n over bidi-pipes.\n\n Will merge to 'master'.\n\n\n* mh/packed-refs-various (2013-05-01) 33 commits\n  (merged to 'next' on 2013-05-01 at e527153)\n + refs: handle the main ref_cache specially\n + refs: change do_for_each_*() functions to take ref_cache arguments\n + pack_one_ref(): do some cheap tests before a more expensive one\n + pack_one_ref(): use write_packed_entry() to do the writing\n + pack_one_ref(): use function peel_entry()\n + refs: inline function do_not_prune()\n + pack_refs(): change to use do_for_each_entry()\n + refs: use same lock_file object for both ref-packing functions\n + pack_one_ref(): rename \"path\" parameter to \"refname\"\n + pack-refs: merge code from pack-refs.{c,h} into refs.{c,h}\n + pack-refs: rename handle_one_ref() to pack_one_ref()\n + refs: extract a function write_packed_entry()\n + repack_without_ref(): write peeled refs in the rewritten file\n + t3211: demonstrate loss of peeled refs if a packed ref is deleted\n + refs: change how packed refs are deleted\n + search_ref_dir(): return an index rather than a pointer\n + repack_without_ref(): silence errors for dangling packed refs\n + t3210: test for spurious error messages for dangling packed refs\n + refs: change the internal reference-iteration API\n + refs: extract a function peel_entry()\n + peel_ref(): fix return value for non-peelable, not-current reference\n + peel_object(): give more specific information in return value\n + refs: extract function peel_object()\n + refs: extract a function ref_resolves_to_object()\n + repack_without_ref(): use function get_packed_ref()\n + peel_ref(): use function get_packed_ref()\n + get_packed_ref(): return a ref_entry\n + do_for_each_ref_in_dirs(): remove dead code\n + refs: define constant PEELED_LINE_LENGTH\n + refs: document how current_ref is used\n + refs: document do_for_each_ref() and do_one_ref()\n + refs: document the fields of struct ref_value\n + refs: document flags constants REF_*\n (this branch uses jc/prune-all.)\n\n Updates reading and updating packed-refs file, correcting corner\n case bugs.\n\n Will merge to 'master'.\n\n\n* fc/transport-helper-error-reporting (2013-05-10) 12 commits\n  (merged to 'next' on 2013-05-10 at 2a9af4b)\n + transport-helper: fix remote helper namespace regression\n + test: remote-helper: add missing and\n  (merged to 'next' on 2013-04-25 at 3358f1a)\n + t5801: \"VAR=VAL shell_func args\" is forbidden\n  (merged to 'next' on 2013-04-22 at 5ba6467)\n + transport-helper: update remote helper namespace\n + transport-helper: trivial code shuffle\n + transport-helper: warn when refspec is not used\n + transport-helper: clarify pushing without refspecs\n + transport-helper: update refspec documentation\n + transport-helper: clarify *:* refspec\n + transport-helper: improve push messages\n + transport-helper: mention helper name when it dies\n + transport-helper: report errors properly\n (this branch is tangled with js/transport-helper-error-reporting-fix.)\n\n Update transport helper to report errors and maintain ref hierarchy\n used to keep track of remote helper state better.\n\n Will merge to 'master'.\n\n\n* js/transport-helper-error-reporting-fix (2013-04-28) 13 commits\n  (merged to 'next' on 2013-04-29 at 8cc4bb8)\n + git-remote-testgit: build it to run under $SHELL_PATH\n + git-remote-testgit: further remove some bashisms\n + git-remote-testgit: avoid process substitution\n  (merged to 'next' on 2013-04-25 at 3358f1a)\n + t5801: \"VAR=VAL shell_func args\" is forbidden\n  (merged to 'next' on 2013-04-22 at 5ba6467)\n + transport-helper: update remote helper namespace\n + transport-helper: trivial code shuffle\n + transport-helper: warn when refspec is not used\n + transport-helper: clarify pushing without refspecs\n + transport-helper: update refspec documentation\n + transport-helper: clarify *:* refspec\n + transport-helper: improve push messages\n + transport-helper: mention helper name when it dies\n + transport-helper: report errors properly\n (this branch is tangled with fc/transport-helper-error-reporting.)\n\n Finishing touches to fc/transport-helper-error-reporting topic.\n\n Will merge to 'master'.\n\n\n* jk/submodule-subdirectory-ok (2013-04-24) 3 commits\n  (merged to 'next' on 2013-04-24 at 6306b29)\n + submodule: fix quoting in relative_path()\n  (merged to 'next' on 2013-04-22 at f211e25)\n + submodule: drop the top-level requirement\n + rev-parse: add --prefix option\n\n Allow various subcommands of \"git submodule\" to be run not from the\n top of the working tree of the superproject.\n\n Will be commented by Jens.\n\n\n* jl/submodule-mv (2013-04-23) 5 commits\n  (merged to 'next' on 2013-04-23 at c04f574)\n + submodule.c: duplicate real_path's return value\n  (merged to 'next' on 2013-04-19 at 45ae3c9)\n + rm: delete .gitmodules entry of submodules removed from the work tree\n + Teach mv to update the path entry in .gitmodules for moved submodules\n + Teach mv to move submodules using a gitfile\n + Teach mv to move submodules together with their work trees\n\n \"git mv A B\" when moving a submodule A does \"the right thing\",\n inclusing relocating its working tree and adjusting the paths in\n the .gitmodules file.\n\n Will be commented by Jens.\n\n\n* jn/add-2.0-u-A-sans-pathspec (2013-04-26) 1 commit\n - git add: -u/-A now affects the entire working tree\n\n Will cook in 'next' until Git 2.0.\n\n\n* jc/core-checkstat-2.0 (2013-05-06) 1 commit\n - core.statinfo: remove as promised in Git 2.0\n (this branch uses jc/core-checkstat.)\n\n Will cook in 'next' until Git 2.0.\n\n\n* jc/push-2.0-default-to-simple (2013-04-03) 1 commit\n - push: switch default from \"matching\" to \"simple\"\n\n Will cook in 'next' until Git 2.0.\n\n\n* jc/add-2.0-ignore-removal (2013-04-22) 1 commit\n - git add <pathspec>... defaults to \"-A\"\n\n Updated endgame for \"git add <pathspec>\" that defaults to \"--all\"\n aka \"--no-ignore-removal\".\n\n Will cook in 'next' until Git 2.0.\n\n--------------------------------------------------\n[Discarded]\n\n* kb/full-history-compute-treesame-carefully (2013-05-06) 11 commits\n . revision.c: treat A...B merge bases as if manually specified\n . revision.c: discount side branches when computing TREESAME\n . simplify-merges: drop merge from irrelevant side branch\n . simplify-merges: never remove all TREESAME parents\n . t6012: update test for tweaked full-history traversal\n . revision.c: Make --full-history consider more merges\n . rev-list-options.txt: correct TREESAME for P\n . t6111: allow checking the parents as well\n . t6111: new TREESAME test set\n . t6019: test file dropped in -s ours merge\n . decorate.c: compact table when growing\n\n Superseded by kb/full-history-compute-treesame-carefully-2\n"},{"id":"218718","messageId":"51a56e2db218d_807b33e18100177@nysa.mail","threadId":"33963","inReplyTo":"7vli6yydmv.fsf@alter.siamese.dyndns.org","subject":"RE: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2013-05-29T02:55:41Z","receivedAt":"2013-05-29T02:55:41Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Junio C Hamano wrote:\n> * fc/makefile (2013-05-26) 5 commits\n>  - build: do not install git-remote-testpy\n>  - build: add NO_INSTALL variable\n>  - build: cleanup using $<\n>  - build: cleanup using $^\n>  - build: trivial simplification\n>  (this branch is used by fc/remote-helpers-use-specified-python.)\n\nNo, these are independent.\n\n> * fc/remote-helpers-use-specified-python (2013-05-28) 4 commits\n>  - remote-helpers: add exec-path links\n>  - remote-helpers: allow direct test execution\n>  - remote-helpers: rename tests\n>  - remote-helpers: generate scripts\n>  (this branch uses fc/makefile.)\n> \n>  I do not particularly think the second from the bottom is a good\n>  change, but it takes the remainder of the series hostage.\n>  Will hopefully be rerolled without it.\n\n\n> * fc/remote-bzr (2013-05-28) 8 commits\n>  - remote-bzr: add fallback check for a partial clone\n>  - remote-bzr: reorganize the way 'wanted' works\n>  - remote-bzr: trivial cleanups\n>  - remote-bzr: change global repo\n>  - remote-bzr: delay cloning/pulling\n>  - remote-bzr: simplify get_remote_branch()\n>  - remote-bzr: fix for files with spaces\n>  - remote-bzr: recover from failed clones\n> \n>  The ones near the tip conflicted with the hotfix for 1.8.3 so I\n>  discarded them for now.\n> \n>  Will merge to 'next'?\n\nDidn't I resend these with the conflict fixed?\n\n-- \nFelipe Contreras\n"},{"id":"218796","messageId":"1369825880-8608-1-git-send-email-artagnon@gmail.com","threadId":"33963","inReplyTo":"7vli6yydmv.fsf@alter.siamese.dyndns.org","subject":"[PATCH] fixup! rebase: implement --[no-]autostash and rebase.autostash","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2013-05-29T11:11:20Z","receivedAt":"2013-05-29T11:11:20Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"For rr/rebase-autostash, which is stalled in pu.  See $gmane/225689.\n\nThis is a super-minor fix anyway: if you disagree with something, change\nit; there's no need to ask me.\n\nAs for the follow-up introducing a 'stash store', I will submit it in\ngood time: there's no hurry.  I'm working on some other interesting\nthings in the meantime (see hot-branch and @{push}).\n\nThanks.\n\nSigned-off-by: Ramkumar Ramachandra <artagnon@gmail.com>\n---\n git-rebase.sh | 8 ++++----\n 1 file changed, 4 insertions(+), 4 deletions(-)\n\ndiff --git a/git-rebase.sh b/git-rebase.sh\nindex 709ef6b..5906757 100755\n--- a/git-rebase.sh\n+++ b/git-rebase.sh\n@@ -151,16 +151,16 @@ finish_rebase () {\n \t\tstash_sha1=$(cat \"$state_dir/autostash\")\n \t\tif git stash apply $stash_sha1 2>&1 >/dev/null\n \t\tthen\n-\t\t\techo \"Applied autostash\"\n+\t\t\techo \"$(gettext 'Applied autostash.')\"\n \t\telse\n \t\t\tref_stash=refs/stash &&\n \t\t\t: >>\"$GIT_DIR/logs/$ref_stash\" &&\n \t\t\tgit update-ref -m \"autostash\" $ref_stash $stash_sha1 \\\n \t\t\t\t|| die \"$(eval_gettext 'Cannot store $stash_sha1')\"\n-\t\t\techo \"\n-$(gettext 'Applying autostash resulted in conflicts.\n+\t\t\tgettext 'Applying autostash resulted in conflicts.\n Your changes are safe in the stash.\n-You can apply or drop it at any time.')\"\n+You can run \"git stash pop\" or \"git stash drop\" it at any time.\n+'\n \t\tfi\n \tfi\n \tgit gc --auto &&\n-- \n1.8.3.rc3.11.geb5ebca\n"},{"id":"218801","messageId":"CALkWK0m+t9DPrUbGBnaJ7jTqTVHohGgiiR-bjcTTRNmbT-Oq8A@mail.gmail.com","threadId":"33963","inReplyTo":"7vli6yydmv.fsf@alter.siamese.dyndns.org","subject":"Re: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2013-05-29T11:27:44Z","receivedAt":"2013-05-29T11:27:44Z","isPatch":false,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Junio C Hamano wrote:\n> * rr/rebase-autostash (2013-05-12) 7 commits\n>  - rebase: implement --[no-]autostash and rebase.autostash\n>  - rebase --merge: return control to caller, for housekeeping\n>  - rebase -i: return control to caller, for housekeeping\n>  - am: return control to caller, for housekeeping\n>  - rebase: prepare to do generic housekeeping\n>  - rebase -i: don't error out if $state_dir already exists\n>  - am: tighten a conditional that checks for $dotest\n>\n>  This is from v3, but after a \"Fixed\" message in $gmane/224111 we\n>  haven't seen a reroll yet.  Also there was an attempt for a\n>  follow-up, but it was never completed.\n\nI've sent a tiny fixup for the last part.  Let me know if you're\nexpecting something else.\n\n> * rr/die-on-missing-upstream (2013-05-22) 2 commits\n>  - sha1_name: fix error message for @{<N>}, @{<date>}\n>  - sha1_name: fix error message for @{u}\n>\n>  When a reflog notation is used for implicit \"current branch\", we\n>  did not say which branch and worse said \"branch ''\".\n>\n>  Waiting for series of rerolls to settle.\n\nI'm happy with the version in pu, and I don't intend to send any\nre-rolls.  Is there something you're not happy with?\n\nQuick update from my side:\n\n* publish-rev: the @{push} thing is still in the early poc stages.\n\n* for-each-ref-pretty: not ready; working with Duy.\n\n* push-current-head: ready but for the commit message: in your\nopinion, it doesn't \"fix\" anything other than the output.  I'll\nrewrite and submit soon.\n\n* pickaxe-doc: you had some more comments in latest iteration, but the\nreturns from a re-roll are diminishing.  Frankly, the work is too\nboring: the first few iterations were interesting, because I was\nlearning; now, it's mostly differences in taste.  Nevertheless, I'll\nre-roll when I want to sleep next.\n\nThat's about it, I think.  I've abandoned everything else.\n"},{"id":"218858","messageId":"7v4ndlvgnq.fsf@alter.siamese.dyndns.org","threadId":"33963","inReplyTo":"51a56e2db218d_807b33e18100177@nysa.mail","subject":"Re: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-05-29T17:29:13Z","receivedAt":"2013-05-29T17:29:13Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Felipe Contreras <felipe.contreras@gmail.com> writes:\n\n> Junio C Hamano wrote:\n>> * fc/makefile (2013-05-26) 5 commits\n>>  - build: do not install git-remote-testpy\n>>  - build: add NO_INSTALL variable\n>>  - build: cleanup using $<\n>>  - build: cleanup using $^\n>>  - build: trivial simplification\n>>  (this branch is used by fc/remote-helpers-use-specified-python.)\n>\n> No, these are independent.\n\nBy the way, I dropped the order-only one and I explained my\nreasoning for doing so, but I haven't heard back from you.\n\nAs I haven't used the order-only dependencies nor '|' myself so far\n(primarily because I have not seen a case where it was needed), it\nwould have been nice if you responded with either \"yes, this is not\norder-only and the patch should be dropped\", or \"no, order-only is\ncorrect because...\".\n\nIn any case, I think the above remaining five were sensible changes,\nand am thinking about having it graduating early in the cycle.\n\nI somehow had an impression that the other series depended on this\nfor SCRIPT_PYTHON_* stuff, but this is about the installation step\nand the other one is primarily about the build step, so in that\nsense it may be independent.\n\n>> * fc/remote-bzr (2013-05-28) 8 commits\n>>  - remote-bzr: add fallback check for a partial clone\n>>  - remote-bzr: reorganize the way 'wanted' works\n>>  - remote-bzr: trivial cleanups\n>>  - remote-bzr: change global repo\n>>  - remote-bzr: delay cloning/pulling\n>>  - remote-bzr: simplify get_remote_branch()\n>>  - remote-bzr: fix for files with spaces\n>>  - remote-bzr: recover from failed clones\n>> \n>>  The ones near the tip conflicted with the hotfix for 1.8.3 so I\n>>  discarded them for now.\n>> \n>>  Will merge to 'next'?\n>\n> Didn't I resend these with the conflict fixed?\n\nAs the date above (05-28) shows, it seems that I did not forget to\ndrop the old one to replace with the new one, but I did forget to\nremove the stale comment from the previous issue.  Thanks for\nnoticing.\n"},{"id":"218859","messageId":"7vzjvdu1y5.fsf@alter.siamese.dyndns.org","threadId":"33963","inReplyTo":"1369825880-8608-1-git-send-email-artagnon@gmail.com","subject":"Re: [PATCH] fixup! rebase: implement --[no-]autostash and rebase.autostash","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-05-29T17:32:18Z","receivedAt":"2013-05-29T17:32:18Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ramkumar Ramachandra <artagnon@gmail.com> writes:\n\n> For rr/rebase-autostash, which is stalled in pu.  See $gmane/225689.\n>\n> This is a super-minor fix anyway: if you disagree with something, change\n> it; there's no need to ask me.\n\nAs I wasn't the one who were disagreeing, that would not work\nwell.\n\nWas there anybody \"disagreeing\" in the first place?  I thought\neverybody was helping the series to get better.\n\n>  git-rebase.sh | 8 ++++----\n>  1 file changed, 4 insertions(+), 4 deletions(-)\n>\n> diff --git a/git-rebase.sh b/git-rebase.sh\n> index 709ef6b..5906757 100755\n> --- a/git-rebase.sh\n> +++ b/git-rebase.sh\n> @@ -151,16 +151,16 @@ finish_rebase () {\n>  \t\tstash_sha1=$(cat \"$state_dir/autostash\")\n>  \t\tif git stash apply $stash_sha1 2>&1 >/dev/null\n>  \t\tthen\n> -\t\t\techo \"Applied autostash\"\n> +\t\t\techo \"$(gettext 'Applied autostash.')\"\n>  \t\telse\n>  \t\t\tref_stash=refs/stash &&\n>  \t\t\t: >>\"$GIT_DIR/logs/$ref_stash\" &&\n>  \t\t\tgit update-ref -m \"autostash\" $ref_stash $stash_sha1 \\\n>  \t\t\t\t|| die \"$(eval_gettext 'Cannot store $stash_sha1')\"\n> -\t\t\techo \"\n> -$(gettext 'Applying autostash resulted in conflicts.\n> +\t\t\tgettext 'Applying autostash resulted in conflicts.\n>  Your changes are safe in the stash.\n> -You can apply or drop it at any time.')\"\n> +You can run \"git stash pop\" or \"git stash drop\" it at any time.\n> +'\n>  \t\tfi\n>  \tfi\n>  \tgit gc --auto &&\n"},{"id":"218860","messageId":"CALkWK0ndproca_tbs3yg5X2Zw+opDPPRXsd520v6TPVcU4iSfg@mail.gmail.com","threadId":"33963","inReplyTo":"7vzjvdu1y5.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] fixup! rebase: implement --[no-]autostash and rebase.autostash","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2013-05-29T17:38:06Z","receivedAt":"2013-05-29T17:38:06Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Junio C Hamano wrote:\n> As I wasn't the one who were disagreeing, that would not work\n> well.\n\nI meant in the tiny details like echo + gettext versus gettext.\n\n>From the review of v3, nobody had any disagreements; just minor\nsuggestions: that's what this patch is about anyway.\n"},{"id":"218861","messageId":"vpq4ndlbs98.fsf@anie.imag.fr","threadId":"33963","inReplyTo":"7vzjvdu1y5.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] fixup! rebase: implement --[no-]autostash and rebase.autostash","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-05-29T17:38:59Z","receivedAt":"2013-05-29T17:38:59Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Ramkumar Ramachandra <artagnon@gmail.com> writes:\n>\n>> For rr/rebase-autostash, which is stalled in pu.  See $gmane/225689.\n>>\n>> This is a super-minor fix anyway: if you disagree with something, change\n>> it; there's no need to ask me.\n>\n> As I wasn't the one who were disagreeing, that would not work\n> well.\n>\n> Was there anybody \"disagreeing\" in the first place?\n\nI was the one suggesting the change, but I do not disagree with\nanything ;-). The fixup is right.\n\nI think Ramkumar was just saying \"feel free to edit while applying\", not\nthat there was any disagreement actually.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"218862","messageId":"7vvc61u1cc.fsf@alter.siamese.dyndns.org","threadId":"33963","inReplyTo":"CALkWK0m+t9DPrUbGBnaJ7jTqTVHohGgiiR-bjcTTRNmbT-Oq8A@mail.gmail.com","subject":"Re: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2013-05-29T17:45:23Z","receivedAt":"2013-05-29T17:45:23Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ramkumar Ramachandra <artagnon@gmail.com> writes:\n\n>> * rr/die-on-missing-upstream (2013-05-22) 2 commits\n>>  - sha1_name: fix error message for @{<N>}, @{<date>}\n>>  - sha1_name: fix error message for @{u}\n>>\n>>  When a reflog notation is used for implicit \"current branch\", we\n>>  did not say which branch and worse said \"branch ''\".\n>>\n>>  Waiting for series of rerolls to settle.\n>\n> I'm happy with the version in pu, and I don't intend to send any\n> re-rolls.\n\nOK, then I'll take a final look at it (I may or may not have\ncomments after doing so) before merging it down.\n\n> Is there something you're not happy with?\n\nBy the way, you probably should stop thinking in terms of \"me\" being\n(un)happy.  I am just trying to help by preventing (collectively) us\nmaking silly mistakes.\n\n> * publish-rev: the @{push} thing is still in the early poc stages.\n\nI presume this is the one that may someday lay foundations for Tytso's\n\"do not rebase beyond this point, as I have published it already\"?\n\n> * for-each-ref-pretty: not ready; working with Duy.\n\nI haven't been paying too much attention to it, but my impression\nwas a \"superset\" syntax is coming?  That would be going in the right\ndirection.\n\n> * push-current-head: ready but for the commit message: in your\n> opinion, it doesn't \"fix\" anything other than the output.  I'll\n> rewrite and submit soon.\n\nI do not recall what this one is about, but we'll see when you send\nit out.\n\n> * pickaxe-doc: you had some more comments in latest iteration, but the\n> returns from a re-roll are diminishing.  Frankly, the work is too\n> boring: the first few iterations were interesting, because I was\n> learning;...\n\nYeah, some parts of the project is boring and that is not a news.\nThink of documentation updates as helping others to learn.\n"},{"id":"218870","messageId":"CALkWK0kwdm+CP=_EsWgEsBPACnMWpy9-hV5wjdWDXYggCntFpA@mail.gmail.com","threadId":"33963","inReplyTo":"7vvc61u1cc.fsf@alter.siamese.dyndns.org","subject":"Re: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2013-05-29T18:15:32Z","receivedAt":"2013-05-29T18:15:32Z","isPatch":false,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Junio C Hamano wrote:\n>> Is there something you're not happy with?\n>\n> By the way, you probably should stop thinking in terms of \"me\" being\n> (un)happy.  I am just trying to help by preventing (collectively) us\n> making silly mistakes.\n\nAs a general principle, okay.\n\nIIRC, nobody else had comments on this one.\n\n>> * publish-rev: the @{push} thing is still in the early poc stages.\n>\n> I presume this is the one that may someday lay foundations for Tytso's\n> \"do not rebase beyond this point, as I have published it already\"?\n\nYep.  More importantly, I'll get something I've been wanting badly:\nthe tracking info in the prompt.\n\n>> * for-each-ref-pretty: not ready; working with Duy.\n>\n> I haven't been paying too much attention to it, but my impression\n> was a \"superset\" syntax is coming?  That would be going in the right\n> direction.\n\nYes, a superset with coming with one caveat: %ae will be interpreted\nas hex.  I hope to send a large'ish series that also strips out the\n-v, -vv code.  Duy basically did most of the work by coming up with a\nbrilliant way to inject into the pretty-formats machinery.\n\n>> * pickaxe-doc: you had some more comments in latest iteration, but the\n>> returns from a re-roll are diminishing.  Frankly, the work is too\n>> boring: the first few iterations were interesting, because I was\n>> learning;...\n>\n> Yeah, some parts of the project is boring and that is not a news.\n> Think of documentation updates as helping others to learn.\n\nSee, the problem is that I might drop the ball on patches like this\n(I've done it before, when I thought the change wasn't important\nenough for me to bore myself).  This is definitely important, and I\nwill see it to completion.  But I'm echoing a more general problem:\n\nIf people don't feel like working on it, how will the documentation\nimprove?  And if the pickaxe-doc was in such bad shape, how could\nanyone have been using it?  Do an internet search and see for\nyourself.  This feature is _extremely_ useful, and it's a real shame\nthat it has been so poorly documented for this long.\n\nI'm not advocating a lax review that checks in technically incorrect\ndocumentation; that will confuse users and turn it into a huge\nmaintenance burden.  But we can maybe go down a notch on style?\n"},{"id":"218879","messageId":"51a64cf542ee1_22511551e18464f5@nysa.mail","threadId":"33963","inReplyTo":"7v4ndlvgnq.fsf@alter.siamese.dyndns.org","subject":"Re: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2013-05-29T18:46:13Z","receivedAt":"2013-05-29T18:46:13Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"Junio C Hamano wrote:\n> Felipe Contreras <felipe.contreras@gmail.com> writes:\n> \n> > Junio C Hamano wrote:\n> >> * fc/makefile (2013-05-26) 5 commits\n> >>  - build: do not install git-remote-testpy\n> >>  - build: add NO_INSTALL variable\n> >>  - build: cleanup using $<\n> >>  - build: cleanup using $^\n> >>  - build: trivial simplification\n> >>  (this branch is used by fc/remote-helpers-use-specified-python.)\n> >\n> > No, these are independent.\n> \n> By the way, I dropped the order-only one and I explained my\n> reasoning for doing so, but I haven't heard back from you.\n> \n> As I haven't used the order-only dependencies nor '|' myself so far\n> (primarily because I have not seen a case where it was needed), it\n> would have been nice if you responded with either \"yes, this is not\n> order-only and the patch should be dropped\", or \"no, order-only is\n> correct because...\".\n\nI'm not sure, so I think it's OK to drop it. I've used order-only to\ndependencies that should not be listed when doing $^ which doesn't affect us\nanyway, so I thought it was more descriptive with the patch, but I can see why\nit would break the build if that file is updated and the targets that depend on\nit don't.\n\nI don't have time to investigate further, so I think it's OK.\n\n> In any case, I think the above remaining five were sensible changes,\n> and am thinking about having it graduating early in the cycle.\n\nIf you do that, please add git-remote-testgit.sh to the NO_INSTALL list. I\ndidn't do that at the time because I was working on the master branch, but this\nchanged in 'next'.\n\n> I somehow had an impression that the other series depended on this\n> for SCRIPT_PYTHON_* stuff, but this is about the installation step\n> and the other one is primarily about the build step, so in that\n> sense it may be independent.\n\nThey are completely independent. The improvments to the main Makefile is what I\ncame up while trying to understand the code.\n\n> >> * fc/remote-bzr (2013-05-28) 8 commits\n> >>  - remote-bzr: add fallback check for a partial clone\n> >>  - remote-bzr: reorganize the way 'wanted' works\n> >>  - remote-bzr: trivial cleanups\n> >>  - remote-bzr: change global repo\n> >>  - remote-bzr: delay cloning/pulling\n> >>  - remote-bzr: simplify get_remote_branch()\n> >>  - remote-bzr: fix for files with spaces\n> >>  - remote-bzr: recover from failed clones\n> >> \n> >>  The ones near the tip conflicted with the hotfix for 1.8.3 so I\n> >>  discarded them for now.\n> >> \n> >>  Will merge to 'next'?\n> >\n> > Didn't I resend these with the conflict fixed?\n> \n> As the date above (05-28) shows, it seems that I did not forget to\n> drop the old one to replace with the new one, but I did forget to\n> remove the stale comment from the previous issue.  Thanks for\n> noticing.\n\nOh, I see. Cool.\n\n-- \nFelipe Contreras\n"},{"id":"218911","messageId":"51A692F4.5080805@ramsay1.demon.co.uk","threadId":"33963","inReplyTo":"7vli6yydmv.fsf@alter.siamese.dyndns.org","subject":"Re: What's cooking in git.git (May 2013, #08; Tue, 28)","fromName":"Ramsay Jones","fromEmail":"ramsay@ramsay1.demon.co.uk","sentAt":"2013-05-29T23:44:52Z","receivedAt":"2013-05-29T23:44:52Z","isPatch":false,"sender":{"key":"ramsay@ramsayjones.plus.com","avatar":"https://avatars.githubusercontent.com/u/33702710?v=4"},"body":"Junio C Hamano wrote:\n> \n> * rj/mingw-compat-st-mode-bits (2013-05-28) 1 commit\n>  - path: Fix a sparse warning\n> \n>  Will merge to 'next'.\n\nHmm, this breaks the build on cygwin. :(\n\nNow, I always test my patches on Linux, cygwin and MinGW\nbefore sending, ... except that I obviously didn't test\non cygwin this time - it doesn't even compile. *ahem*\n\nThe extern declaration for get_st_mode_bits() must come\n*before* including compat/cygwin.h; otherwise it will\nget mangled by the macro in that header file.\n\nSorry for breaking the build.\n\nA v3 patch is on it's way. (I'm liking the v1 patch more now ;-)\n\nATB,\nRamsay Jones\n"}]}