{"thread":{"id":"18892","subject":"What's cooking in git.git (Apr 2009, #03; Wed, 15)","startedAt":"2009-04-16T05:47:04Z","lastAt":"2009-04-17T20:34:25Z","messageCount":3,"participants":["Junio C Hamano","Michael Witten","Michał Kiedrowicz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"111418","messageId":"7v1vrtno9z.fsf@gitster.siamese.dyndns.org","threadId":"18892","inReplyTo":null,"subject":"What's cooking in git.git (Apr 2009, #03; Wed, 15)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-04-16T05:47:04Z","receivedAt":"2009-04-16T05:47:04Z","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 '-' are\nonly in 'pu' while commits prefixed with '+' are in 'next'.  The ones\nmarked with '.' do not appear in any of the branches, but I am still\nholding onto them.\n\nThe topics list the commits in reverse chronological order.  The topics\nmeant to be merged to the maintenance series have \"maint-\" in their names.\n\nWe are a bit past 1.6.3-rc0, and this report will show pretty much what\nthe final should look like from the feature-set point-of-view.\n\n----------------------------------------------------------------\n[New Topics]\n\n* ac/color-graph (Mon Apr 13 15:53:41 2009 -0400) 1 commit\n + graph API: Added logic for colored edges\n\nThis has been under discussion since before 1.6.3-rc0, hopefully in\n1.6.3-rc1.\n\n* mw/send-email (Mon Apr 13 13:23:52 2009 -0500) 6 commits\n - send-email: Remove superfluous `my $editor = ...'\n - send-email: 'References:' should only reference what is sent\n - send-email: Handle \"GIT:\" rather than \"GIT: \" during --compose\n - Docs: send-email: --smtp-server-port can take symbolic ports\n - Docs: send-email: Refer to CONFIGURATION section for\n   sendemail.multiedit\n - Docs: send-email: Put options back into alphabetical order\n\nOnly partially queued, but this is not 1.6.3 material and we are not in a\nhurry.\n\n* jk/cobdoc (Mon Apr 13 07:21:04 2009 -0400) 5 commits\n + docs/checkout: clarify what \"non-branch\" means\n + doc/checkout: split checkout and branch creation in synopsis\n + doc/checkout: refer to git-branch(1) as appropriate\n + doc: refer to tracking configuration as \"upstream\"\n + doc: clarify --no-track option\n\nFor 1.6.3\n\n* mk/apply-swap (Sat Apr 11 21:31:00 2009 +0200) 2 commits\n + builtin-apply: keep information about files to be deleted\n + tests: test applying criss-cross rename patch\n\nFor 1.6.3; perhaps needs to be cherry-picked to 1.6.2.X series as well.\n\n----------------------------------------------------------------\n[Will merge to 'master' before 1.6.3-rc1]\n\n* mm/add-p-quit (Fri Apr 10 16:57:01 2009 +0200) 1 commit\n + git add -p: new \"quit\" command at the prompt.\n\nI did a minimal documentation update myself.\n\n* eb/upload-archive-from-git-shell (Thu Apr 9 21:58:52 2009 +0200) 1 commit\n + git-shell: Add 'git-upload-archive' to allowed commands.\n\n* jc/shared-literally (Sun Apr 12 17:55:18 2009 -0700) 2 commits\n + Mark t1301 permission test to depend on POSIXPERM\n + t1301-shared-repo: fix forced modes test\n\n* jc/maint-shared-literally (Sun Apr 12 21:22:02 2009 +0200) 1 commit\n + t1301-shared-repo: fix forced modes test\n\nJ6t's updates to fix permission tests and make sure they won't run on\nsystems without permission bits on the filesystem.\n\n* ns/am-to-empty (Fri Apr 10 09:34:42 2009 +0900) 1 commit\n + git-am: teach git-am to apply a patch to an unborn branch\n\n* bw/short-ref-strict (Mon Apr 13 13:20:26 2009 +0200) 3 commits\n + rev-parse: --abbrev-ref option to shorten ref name\n + for-each-ref: utilize core.warnAmbiguousRefs for :short-format\n + shorten_unambiguous_ref(): add strict mode\n\n* da/difftool (Sat Apr 11 20:41:56 2009 -0700) 16 commits\n + mergetool--lib: simplify API usage by removing more global\n   variables\n + Fix misspelled mergetool.keepBackup\n + difftool/mergetool: refactor commands to use git-mergetool--lib\n + mergetool: use $( ... ) instead of `backticks`\n + bash completion: add git-difftool\n + difftool: add support for a difftool.prompt config variable\n + difftool: add various git-difftool tests\n + difftool: move 'git-difftool' out of contrib\n + difftool/mergetool: add diffuse as merge and diff tool\n + difftool: add a -y shortcut for --no-prompt\n + difftool: use perl built-ins when testing for msys\n + difftool: remove the backup file feature\n + difftool: remove merge options for opendiff, tkdiff, kdiff3 and\n   xxdiff\n + git-mergetool: add new merge tool TortoiseMerge\n + git-mergetool/difftool: make (g)vimdiff workable under Windows\n + doc/merge-config: list ecmerge as a built-in merge tool\n\n----------------------------------------------------------------\n[Graduated to \"master\"]\n\n(none)\n\n----------------------------------------------------------------\n[Stalled and may need help and prodding to go forward]\n\n* lt/bool-on-off (Thu Apr 9 12:40:39 2009 -0700) 1 commit\n + Allow users to un-configure rename detection\n\nStill lacks doc updates.\n\n* ps/blame (Thu Mar 12 21:30:03 2009 +1100) 1 commit\n - blame.c: start libifying the blame infrastructure\n\nA few minor point remains in this initial one.  I hate to do these minor\nfix-ups myself, but I may end up doing so...\n\n* jc/log-tz (Tue Mar 3 00:45:37 2009 -0800) 1 commit\n - Allow --date=local --date=other-format to work as expected\n\nThe one I posted had a few corner-case bugs that was caught with the test\nsuite; this one has them fixed.  People did not like the UI so it is kept\nout of 'next'\n\n* jc/merge-convert (Mon Jan 26 16:45:01 2009 -0800) 1 commit\n - git-merge-file: allow converting the results for the work tree\n\nThis is a feature waiting for a user.\n\nWe did not give scripted Porcelains a way to say \"this temporary file I am\nusing for merging is for this path, so use the core.autocrlf and attributes\nrules for that final path\".  Instead, merge-file simply wrote out the\ndata in the canonical repository representation.\n\nrerere has the same issue, but it is a lot worse.  It reads the three\nfiles (preimage, postimage and thisimage) from the work tree in the work\ntree representation, merges them without converting them to the canonical\nrepresentation first but inserts the conflict markers with the canonical\nrepresentation and writes the resulting mess out.  It needs to be fixed to\nread with convert_to_git(), merge them while they are still in the\ncanonical representation and possibly add conflict markers, and then write\nthe results out after convert_to_working_tree().  It also needs to write\nin binary mode as well.\n\n* db/foreign-scm (Tue Mar 24 23:04:12 2009 -0400) 3 commits\n - Add option for using a foreign VCS\n - Document details of transport function APIs\n - Allow late reporting of fetched hashes\n\n* js/notes (Tue Apr 14 00:03:36 2009 +0200) 15 commits\n - Documentation: fix 'linkgit' macro in \"git-notes.txt\"\n - tests: fix \"export var=val\"\n - notes: refuse to edit notes outside refs/notes/\n - t3301: use test_must_fail instead of !\n - t3301: fix confusing quoting in test for valid notes ref\n - notes: use GIT_EDITOR and core.editor over VISUAL/EDITOR\n - notes: only clean up message file when editing\n - handle empty notes gracefully\n - git notes show: test empty notes\n - git-notes: fix printing of multi-line notes\n - notes: fix core.notesRef documentation\n - Add an expensive test for git-notes\n - Speed up git notes lookup\n - Add a script to edit/inspect notes\n - Introduce commit notes\n\n* hv/cvsps-tests (Sun Apr 5 01:40:50 2009 -0700) 8 commits\n - t/t9600: remove exit after test_done\n - cvsimport: extend testcase about patchset order to contain\n   branches\n - cvsimport: add test illustrating a bug in cvsps\n + Add a test of \"git cvsimport\"'s handling of tags and branches\n + Add some tests of git-cvsimport's handling of vendor branches\n + Test contents of entire cvsimported \"master\" tree contents\n + Use CVS's -f option if available (ignore user's ~/.cvsrc file)\n + Start a library for cvsimport-related tests\n\nTwo cvsimport test topics were rewound from 'next' and merged into this\none.  I'll keep this in 'pu' so that people can polish their cvsps skilz\nto resolve issues these tests identify.\n\n----------------------------------------------------------------\n[Actively cooking]\n\n* lt/pack-object-memuse (Fri Apr 10 18:15:26 2009 -0700) 2 commits\n + show_object(): push path_name() call further down\n + process_{tree,blob}: show objects without buffering\n\nThis had some conflicts with Christian's bisect topic; I think I resolved\nthem correctly, but double-checking would be nice.\n\n* nd/archive-attribute (Mon Apr 13 14:18:39 2009 +0200) 5 commits\n + archive test: test new --fix-attributes feature\n + archive: do not read .gitattributes in working directory\n + unpack-trees: do not muck with attributes when we are not checking\n   out\n + attr: add GIT_ATTR_INDEX \"direction\"\n + archive tests: do not use .gitattributes in working directory\n\nWith fix-ups from René and myself.  Perhaps 1.6.3 material, perhaps not.\n\n* js/add-edit (Wed Apr 8 23:30:24 2009 +0200) 1 commit\n - git-add: introduce --edit (to edit the diff vs. the index)\n\n* cc/replace (Tue Apr 14 00:36:59 2009 +0200) 13 commits\n - Documentation: add documentation for \"git replace\"\n - Add git-replace to .gitignore\n - builtin-replace: use \"usage_msg_opt\" to give better error messages\n - parse-options: add new function \"usage_msg_opt\"\n - builtin-replace: teach \"git replace\" to actually replace\n - Add new \"git replace\" command\n - environment: add global variable to disable replacement\n - mktag: call \"check_sha1_signature\" with the replacement sha1\n - replace_object: add a test case\n - object: call \"check_sha1_signature\" with the replacement sha1\n - sha1_file: add a \"read_sha1_file_repl\" function\n - replace_object: add mechanism to replace objects found in\n   \"refs/replace/\"\n - refs: add a \"for_each_replace_ref\" function\n\nI suspect an attempt to replace an object that is directly listed on the\ncommand line would not work very well with this series.\n\n----------------------------------------------------------------\n[Reverted]\n\n* mh/cvsimport-tests (Mon Feb 23 06:08:14 2009 +0100) 5 commits\n + Add a test of \"git cvsimport\"'s handling of tags and branches\n + Add some tests of git-cvsimport's handling of vendor branches\n + Test contents of entire cvsimported \"master\" tree contents\n + Use CVS's -f option if available (ignore user's ~/.cvsrc file)\n + Start a library for cvsimport-related tests\n\nThis has been reverted out of 'next' for some time now.\n\n----------------------------------------------------------------\n[On Hold]\n\n* jc/deny-delete-current-1.7.0 (Mon Feb 9 00:19:46 2009 -0800) 1 commit\n - receive-pack: default receive.denyDeleteCurrent to refuse\n\n* jc/refuse-push-to-current-1.7.0 (Wed Feb 11 02:28:03 2009 -0800) 1 commit\n - Refuse updating the current branch in a non-bare repository via\n   push\n\nThese are for 1.7.0, but the messages when they trigger together may need\nto be rethought.\n"},{"id":"111455","messageId":"b4087cc50904160820t58534dbk3e4219c1713676ac@mail.gmail.com","threadId":"18892","inReplyTo":"7v1vrtno9z.fsf@gitster.siamese.dyndns.org","subject":"Re: What's cooking in git.git (Apr 2009, #03; Wed, 15)","fromName":"Michael Witten","fromEmail":"mfwitten@gmail.com","sentAt":"2009-04-16T15:20:27Z","receivedAt":"2009-04-16T15:20:27Z","isPatch":false,"sender":{"key":"mfwitten@gmail.com","avatar":"https://avatars.githubusercontent.com/u/597101?v=4"},"body":"On Thu, Apr 16, 2009 at 00:47, Junio C Hamano <gitster@pobox.com> wrote:\n>  - Docs: send-email: --smtp-server-port can take symbolic ports\n\nI've done a little more reading, and I think that 'service names' is\nbetter than 'symbolic ports'. Also, the text you added, '(e.g.\n\"submission\" instead of 465)', should probably be '(e.g. submission\ninstead of 587)' in order to match up with IANA's mappings.\n\nI've got another patch in which these changes are a part, so you can\njust leave things as is and let the next patch fix them up.\n"},{"id":"111535","messageId":"20090417223425.1abb78fa@gmail.com","threadId":"18892","inReplyTo":"7v1vrtno9z.fsf@gitster.siamese.dyndns.org","subject":"[PATCH] Documentation: boolean value may be given by on/off","fromName":"Michał Kiedrowicz","fromEmail":"michal.kiedrowicz@gmail.com","sentAt":"2009-04-17T20:34:25Z","receivedAt":"2009-04-17T20:34:25Z","isPatch":true,"sender":{"key":"michal.kiedrowicz@gmail.com","avatar":"https://avatars.githubusercontent.com/u/14072847?v=4"},"body":"Junio C Hamano <gitster@pobox.com> wrote:\n\n> ----------------------------------------------------------------\n> [Stalled and may need help and prodding to go forward]\n> \n> * lt/bool-on-off (Thu Apr 9 12:40:39 2009 -0700) 1 commit\n>  + Allow users to un-configure rename detection\n> \n> Still lacks doc updates.\n>\n\nSigned-off-by: Michał Kiedrowicz <michal.kiedrowicz@gmail.com>\n---\n Documentation/config.txt |    6 +++---\n 1 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/config.txt b/Documentation/config.txt\nindex 5319df5..1c64683 100644\n--- a/Documentation/config.txt\n+++ b/Documentation/config.txt\n@@ -61,7 +61,7 @@ Internal whitespace within a variable value is retained verbatim.\n\n The values following the equals sign in variable assign are all either\n a string, an integer, or a boolean.  Boolean values may be given as yes/no,\n-0/1 or true/false.  Case is not significant in boolean values, when\n+0/1, true/false or on/off.  Case is not significant in boolean values, when\n converting value to the canonical form using '--bool' type specifier;\n 'git-config' will ensure that the output is \"true\" or \"false\".\n\n@@ -945,8 +945,8 @@ guitool.<name>.argprompt::\n        Request a string argument from the user, and pass it to the tool\n        through the 'ARGS' environment variable. Since requesting an\n        argument implies confirmation, the 'confirm' option has no effect\n-       if this is enabled. If the option is set to 'true', 'yes', or '1',\n-       the dialog uses a built-in generic prompt; otherwise the exact\n+       if this is enabled. If the option is set to 'true', 'yes', 'on' or\n+       '1', the dialog uses a built-in generic prompt; otherwise the exact\n        value of the variable is used.\n\n guitool.<name>.revprompt::\n-- \n1.6.0.6\n"}]}