{"thread":{"id":"35022","subject":"What's cooking in git.git (Sep 2013, #08; Wed, 25)","startedAt":"2013-09-25T23:41:21Z","lastAt":"2013-09-27T17:52:58Z","messageCount":6,"participants":["Jonathan Nieder","Torsten Bögershausen","Jiang Xin","Matthieu Moy","Philip Oakley"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"228239","messageId":"20130925234121.GD9464@google.com","threadId":"35022","inReplyTo":null,"subject":"What's cooking in git.git (Sep 2013, #08; Wed, 25)","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-09-25T23:41:21Z","receivedAt":"2013-09-25T23:41:21Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"What's cooking in git.git (Sep 2013, #08; Wed, 25)\n--------------------------------------------------\n\nHere 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\nThe fifth batch of topics are in 'master'.\n\nYou can find the changes described here in the integration branches at\n\n    git://repo.or.cz/git/jrn.git\n    http://repo.or.cz/r/git/jrn.git\n\nOr view the web interface:\n\n    http://repo.or.cz/w/git/jrn.git\n\nI'll probably be releasing 1.8.4.1 tomorrow.  If you have time to\nexperiment with \"maint\" or \"master\" to find any remaining problems\nuntil then, that will be very welcome.\n\n--------------------------------------------------\n[Graduated to \"master\"]\n\n* bc/submodule-status-ignored (2013-09-11) 3 commits\n  (merged to 'next' on 2013-09-11 at 9f66712)\n + Improve documentation concerning the status.submodulesummary setting\n  (merged to 'next' on 2013-09-10 at a417960)\n + submodule: don't print status output with ignore=all\n + submodule: fix confusing variable name\n\n\n* bp/mediawiki-infinite-loop-fix (2013-09-23) 1 commit\n - git-remote-mediawiki: bugfix for pages w/ >500 revisions\n\n The mediawiki:: remote helper would hang while handling results from\n queries with more than 500 results against version 1.21 or newer of\n the Mediawiki server.\n\n\n* cc/replace-with-the-same-type (2013-09-09) 8 commits\n  (merged to 'next' on 2013-09-17 at 34b5bb7)\n + Doc: 'replace' merge and non-merge commits\n + t6050-replace: use some long option names\n + replace: allow long option names\n + Documentation/replace: add Creating Replacement Objects section\n + t6050-replace: add test to clean up all the replace refs\n + t6050-replace: test that objects are of the same type\n + Documentation/replace: state that objects must be of the same type\n + replace: forbid replacing an object with one of a different type\n\n Using the replace mechanism to swap an object with another object\n of a different type can introduce inconsistency (e.g. a tree\n expects an object name to refer to a blob, but the blob object can\n be mistakenly or maliciously replaced with an object with a\n different type). Attempt to forbid such.\n\n\n* es/contacts-in-subdir (2013-09-17) 1 commit\n  (merged to 'next' on 2013-09-20 at d67164f)\n + contacts: fix to work in subdirectories\n\n Allows the contacts (in contrib/) script to run from inside a\n subdirectory.\n\n\n* jc/push-cas (2013-09-20) 1 commit\n  (merged to 'next' on 2013-09-20 at 5e1e7cc)\n + t5541: mark passing c-a-s test as success\n\n A touch-up to finish off a recently added feature.\n\n\n* jc/strcasecmp-pure-inline (2013-09-12) 1 commit\n  (merged to 'next' on 2013-09-20 at 7142d08)\n + mailmap: work around implementations with pure inline strcasecmp\n\n Work around MinGW <string.h> header that does not declare strcasecmp\n whose address cannot be taken.\n\n\n* jk/shortlog-tolerate-broken-commit (2013-09-18) 1 commit\n  (merged to 'next' on 2013-09-20 at 9c85c02)\n + shortlog: ignore commits with missing authors\n\n\n* kb/msvc-compile (2013-09-11) 5 commits\n  (merged to 'next' on 2013-09-17 at a9bcbb5)\n + Windows: do not redefine _WIN32_WINNT\n + MinGW: Fix stat definitions to work with MinGW runtime version 4.0\n + MSVC: fix stat definition hell\n + MSVC: fix compile errors due to macro redefinitions\n + MSVC: fix compile errors due to missing libintl.h\n\n Build updates for Windows port.\n\n\n* nd/fetch-pack-error-reporting-fix (2013-09-18) 1 commit\n  (merged to 'next' on 2013-09-20 at fefa04f)\n + fetch-pack.c: show correct command name that fails\n\n When \"fetch-pack\" detected an error from spawned \"index-pack\" or\n \"unpack-objects\", it did not report the failed program name\n correctly when a shallow repository is involved.\n\n\n* nd/unpack-entry-optim-in-pack-objects (2013-09-13) 1 commit\n  (merged to 'next' on 2013-09-17 at 00f7335)\n + pack-objects: no crc check when the cached version is used\n\n The codepath to use data from packfiles that is only exercised in\n pack-objects unnecessarily checked crc checksum of the pack data,\n even when it ends up using in-core copy that it got by reading from\n the pack (at which point the checksum was validated).\n\n\n* sg/complete-untracked-filter (2013-09-19) 1 commit\n  (merged to 'next' on 2013-09-20 at 798d0b9)\n + completion: improve untracked directory filtering for filename completion\n\n--------------------------------------------------\n[New Topics]\n\n* bc/gnome-keyring (2013-09-23) 15 commits\n - contrib/git-credential-gnome-keyring.c: support really ancient gnome-keyring\n - contrib/git-credential-gnome-keyring.c: support ancient gnome-keyring\n - contrib/git-credential-gnome-keyring.c: report failure to store password\n - contrib/git-credential-gnome-keyring.c: use glib messaging functions\n - contrib/git-credential-gnome-keyring.c: use glib memory allocation functions\n - contrib/git-credential-gnome-keyring.c: use secure memory for reading passwords\n - contrib/git-credential-gnome-keyring.c: use secure memory functions for passwds\n - contrib/git-credential-gnome-keyring.c: use gnome helpers in keyring_object()\n - contrib/git-credential-gnome-keyring.c: ensure buffer is non-empty before accessing\n - contrib/git-credential-gnome-keyring.c: strlen() returns size_t, not ssize_t\n - contrib/git-credential-gnome-keyring.c: set Gnome application name\n - contrib/git-credential-gnome-keyring.c: exit non-zero when called incorrectly\n - contrib/git-credential-gnome-keyring.c: add static where applicable\n - contrib/git-credential-gnome-keyring.c: remove unused die() function\n - contrib/git-credential-gnome-keyring.c: remove unnecessary pre-declarations\n\n Cleanups and tweaks for credential handling to work with ancient versions\n of the gnome-keyring library that are still in use.\n\n This is version 1 of the series, to give it more exposure.  Waiting for\n the series to stabilize before including in 'next'.\n\n\n* kb/fast-hashmap (2013-09-25) 6 commits\n - fixup! diffcore-rename.c: simplify finding exact renames\n - diffcore-rename.c: use new hash map implementation\n - diffcore-rename.c: simplify finding exact renames\n - diffcore-rename.c: move code around to prepare for the next patch\n - buitin/describe.c: use new hash map implementation\n - add a hashtable implementation that supports O(1) removal\n\n Improvements to our hash table to get it to meet the needs of the\n msysgit fscache project, with some nice performance improvements.\n \n Looks promising.  Needs style review and a sanity-check on the\n design before including in 'next'.  Expecting a reroll once review\n settles down.\n\n--------------------------------------------------\n[Stalled]\n\n* tr/merge-recursive-index-only (2013-07-07) 3 commits\n - merge-recursive: -Xindex-only to leave worktree unchanged\n - merge-recursive: untangle double meaning of o->call_depth\n - merge-recursive: remove dead conditional in update_stages()\n\n Will hold until there is a caller to learn from.\n\n\n* jc/ref-excludes (2013-09-03) 2 commits\n - document --exclude option\n - revision: introduce --exclude=<glob> to tame wildcards\n\n People often wished a way to tell \"git log --branches\" (and \"git\n log --remotes --not --branches\") to exclude some local branches\n from the expansion of \"--branches\" (similarly for \"--tags\", \"--all\"\n and \"--glob=<pattern>\").  Now they have one.\n\n Needs a matching change to rev-parse.\n\n\n* rv/send-email-cache-generated-mid (2013-08-21) 2 commits\n - git-send-email: Cache generated message-ids, use them when prompting\n - git-send-email: add optional 'choices' parameter to the ask sub\n\n\n* rj/read-default-config-in-show-ref-pack-refs (2013-06-17) 3 commits\n - ### DONTMERGE: needs better explanation on what config they need\n - pack-refs.c: Add missing call to git_config()\n - show-ref.c: Add missing call to git_config()\n\n The changes themselves are probably good, but it is unclear what\n basic setting needs to be read for which exact operation.\n\n Waiting for clarification.\n $gmane/228294\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 $gmane/225137\n\n\n* mg/more-textconv (2013-05-10) 7 commits\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 There was a question about how defaulting to 'git show --textconv'\n would interact with the \"git show HEAD:file.c >file.c\" habit.\n $gmane/221833\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\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 Drew Northup volunteered to take a look into this.\n $gmane/226216\n\n\n* jc/show-branch (2013-06-07) 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\n Waiting for the final step to lift the hard-limit before sending it out.\n\n--------------------------------------------------\n[Cooking]\n\n* jc/revision-range-unpeel (2013-09-20) 2 commits\n - (possible fixup) jc/revision-range-unpeel - peel only when necessary\n - revision: do not peel tags used in range notation\n\n \"git rev-list --objects ^v1.0^ v1.0\" gave v1.0 tag itself in the\n output, but \"git rev-list --objects v1.0^..v1.0\" did not.\n\n Need to decide either squashing the top fixup in, or dropping it\n and then merge to 'next'.\n\n\n* tg/perf-lib-test-perf-cleanup (2013-09-19) 2 commits\n - perf-lib: add test_perf_cleanup target\n - perf-lib: split starting the test from the execution\n\n Add test_perf_cleanup shell function to the perf suite, that allows\n the script writers to define a test with a clean-up action.\n\n Holding until needed.\n\n\n* jk/format-patch-from (2013-09-20) 1 commit\n  (merged to 'next' on 2013-09-20 at 0506530)\n + format-patch: print in-body \"From\" only when needed\n\n \"format-patch --from=<whom>\" forgot to omit unnecessary in-body\n from line, i.e. when <whom> is the same as the real author.\n\n Will merge to 'master'.\n\n\n* es/name-hash-no-trailing-slash-in-dirs (2013-09-17) 4 commits\n  (merged to 'next' on 2013-09-20 at 9633d9a)\n + dir: revert work-around for retired dangerous behavior\n + name-hash: stop storing trailing '/' on paths in index_state.dir_hash\n + employ new explicit \"exists in index?\" API\n + name-hash: refactor polymorphic index_name_exists()\n\n Clean up the internal of the name-hash mechanism used to work\n around case insensitivity on some filesystems to cleanly fix a\n long-standing API glitch where the caller of cache_name_exists()\n that ask about a directory with a counted string was required to\n have '/' at one location past the end of the string.\n\n Will merge to 'master'.\n\n\n* po/dot-url (2013-09-13) 2 commits\n  (merged to 'next' on 2013-09-20 at 6a12786)\n + config doc: update dot-repository notes\n + doc: command line interface (cli) dot-repository dwimmery\n\n Explain how '.' can be used to refer to the \"current repository\"\n in the documentation.\n\n Will merge to 'master'.\n\n\n* jc/upload-pack-send-symref (2013-09-17) 7 commits\n - clone: test the new HEAD detection logic\n - connect: annotate refs with their symref information in get_remote_head()\n - connect.c: make parse_feature_value() static\n - upload-pack: send non-HEAD symbolic refs\n - upload-pack: send symbolic ref information as capability\n - upload-pack.c: do not pass confusing cb_data to mark_our_ref()\n - t5505: fix \"set-head --auto with ambiguous HEAD\" test\n\n One long-standing flaw in the pack transfer protocol used by \"git\n clone\" was that there was no way to tell the other end which branch\n \"HEAD\" points at, and the receiving end needed to guess.  A new\n capability has been defined in the pack protocol to convey this\n information so that cloning from a repository with more than one\n branches pointing at the same commit where the HEAD is at now\n reliably sets the initial branch in the resulting repository.\n\n Will merge to 'next'.\n\n\n* jk/clone-progress-to-stderr (2013-09-18) 3 commits\n  (merged to 'next' on 2013-09-25 at 137af9e)\n + clone: always set transport options\n + clone: treat \"checking connectivity\" like other progress\n + clone: send diagnostic messages to stderr\n\n Some progress and diagnostic messages from \"git clone\" were\n incorrectly sent to the standard output stream, not to the standard\n error stream.\n\n Will merge to 'master'.\n\n\n* jx/relative-path-regression-fix (2013-09-20) 3 commits\n - Use simpler relative_path when set_git_dir\n - relative_path should honor dos-driver-prefix\n - test: use unambigous leading path (/foo) for mingw\n\n Waiting for the review to settle.\n\n\n* jc/checkout-detach-doc (2013-09-11) 1 commit\n  (merged to 'next' on 2013-09-17 at 438cf13)\n + checkout: update synopsys and documentation on detaching HEAD\n\n \"git checkout [--detach] <commit>\" was listed poorly in the\n synopsis section of its documentation.\n\n Will merge to 'master'.\n\n\n* jk/trailing-slash-in-pathspec (2013-09-13) 2 commits\n  (merged to 'next' on 2013-09-17 at 18fe277)\n + reset: handle submodule with trailing slash\n + rm: re-use parse_pathspec's trailing-slash removal\n\n Code refactoring.\n\n Will merge to 'master'.\n\n\n* lc/filter-branch-too-many-refs (2013-09-12) 1 commit\n  (merged to 'next' on 2013-09-17 at 31cd01a)\n + Allow git-filter-branch to process large repositories with lots of branches.\n\n \"git filter-branch\" in a repository with many refs blew limit of\n command line length.\n\n Will merge to 'master'.\n\n\n* np/pack-v4 (2013-09-18) 90 commits\n - packv4-parse.c: add tree offset caching\n - t1050: replace one instance of show-index with verify-pack\n - index-pack, pack-objects: allow creating .idx v2 with .pack v4\n - unpack-objects: decode v4 trees\n - unpack-objects: allow to save processed bytes to a buffer\n - ...\n\n Nico and Duy advancing the eternal vaporware pack-v4.  This is here\n primarily for wider distribution of the preview edition.\n\n\n* sb/repack-in-c (2013-09-17) 3 commits\n  (merged to 'next' on 2013-09-25 at 7c47036)\n + repack: improve warnings about failure of renaming and removing files\n + repack: retain the return value of pack-objects\n + repack: rewrite the shell script in C\n\n Rerolled, and I think it is in a reasonably good shape.\n\n Will merge to 'master'.\n\n\n* jc/reflog-doc (2013-06-19) 1 commit\n  (merged to 'next' on 2013-09-25 at 4eb0c14)\n + setup_reflog_action: document the rules for using GIT_REFLOG_ACTION\n\n Document rules to use GIT_REFLOG_ACTION variable in the scripted\n Porcelain.  git-rebase--interactive locally violates them, but it\n is a leaf user that does not call out to or dot-source other\n scripts, so it does not urgently need to be fixed.\n\n Will merge to 'master'.\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\n Will cook in 'next' until Git 2.0.\n\n\n* jc/push-2.0-default-to-simple (2013-06-18) 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* jc/hold-diff-remove-q-synonym-for-no-deletion (2013-07-19) 1 commit\n - diff: remove \"diff-files -q\" in a version of Git in a distant future\n\n Will cook in 'next' until a distant future.\n\n--------------------------------------------------\n[Discarded]\n\n* jc/pull-training-wheel (2013-07-19) 1 commit\n  (merged to 'next' on 2013-08-28 at c39bd15)\n + pull: require choice between rebase/merge on non-fast-forward pull\n\n Make \"git pull\" (without arguments that say what branch to\n integrate from where) refuse with \"it does not fast forward; choose\n between 'pull --merge' and 'pull --rebase'\".\n\n This topic has been reverted from 'next'.  Will wait for the\n conclusion of the discussion to seek a more user-friendly\n alternative; it is likely that it will be based on the simpler\n approach Felipe posted earlier.\n"},{"id":"228259","messageId":"5243CFCD.6090604@web.de","threadId":"35022","inReplyTo":"20130925234121.GD9464@google.com","subject":"Re: What's cooking in git.git (Sep 2013, #08; Wed, 25)","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2013-09-26T06:10:21Z","receivedAt":"2013-09-26T06:10:21Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"> * jx/relative-path-regression-fix (2013-09-20) 3 commits\n>  - Use simpler relative_path when set_git_dir\n>  - relative_path should honor dos-driver-prefix\n>  - test: use unambigous leading path (/foo) for mingw\n> \n>  Waiting for the review to settle.\nIs this V3, which is both fixing a regression\nand adding support for UNC path ?\n\nMy understanding is that V2\ncommit 5a515ecc086dd8d0b74b0aff1248f4d1dc87f556\njx/relative-path-regression-fix\ngit://github.com/gitster/git.git\n\n\nis only fixing the regression and \ncould be merged into next, master and possibly maint.\n"},{"id":"228264","messageId":"CANYiYbH924SoWGdNP-f4iZxQxfR=JAywmap__m7FoEqMAYo-GA@mail.gmail.com","threadId":"35022","inReplyTo":"5243CFCD.6090604@web.de","subject":"Re: What's cooking in git.git (Sep 2013, #08; Wed, 25)","fromName":"Jiang Xin","fromEmail":"worldhello.net@gmail.com","sentAt":"2013-09-26T09:00:21Z","receivedAt":"2013-09-26T09:00:21Z","isPatch":false,"sender":{"key":"worldhello.net@gmail.com","avatar":"https://avatars.githubusercontent.com/u/183860?v=4"},"body":"2013/9/26 Torsten Bögershausen <tboegi@web.de>:\n>> * jx/relative-path-regression-fix (2013-09-20) 3 commits\n>>  - Use simpler relative_path when set_git_dir\n>>  - relative_path should honor dos-driver-prefix\n>>  - test: use unambigous leading path (/foo) for mingw\n>>\n>>  Waiting for the review to settle.\n> Is this V3, which is both fixing a regression\n> and adding support for UNC path ?\n\nNo, it's not V3, but is V4 (same like v2, but there are minor updates for\ntest cases and commit logs). See:\n\n * http://thread.gmane.org/gmane.comp.version-control.git/234434/focus=235047\n\nYou may already read my reply:\n\n * http://thread.gmane.org/gmane.comp.version-control.git/234434/focus=235044\n\n>\n> My understanding is that V2\n> commit 5a515ecc086dd8d0b74b0aff1248f4d1dc87f556\n> jx/relative-path-regression-fix\n> git://github.com/gitster/git.git\n>\n>\n> is only fixing the regression and\n> could be merged into next, master and possibly maint.\n>\n\nYes, but commit 5a515ec is precisely V4.\n\n-- \nJiang Xin\n\n-- \n-- \n*** Please reply-to-all at all times ***\n*** (do not pretend to know who is subscribed and who is not) ***\n*** Please avoid top-posting. ***\nThe msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.\n\nYou received this message because you are subscribed to the Google\nGroups \"msysGit\" group.\nTo post to this group, send email to msysgit@googlegroups.com\nTo unsubscribe from this group, send email to\nmsysgit+unsubscribe@googlegroups.com\nFor more options, and view previous threads, visit this group at\nhttp://groups.google.com/group/msysgit?hl=en_US?hl=en\n\n--- \nYou received this message because you are subscribed to the Google Groups \"msysGit\" group.\nTo unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.\nFor more options, visit https://groups.google.com/groups/opt_out.\n"},{"id":"228269","messageId":"vpqr4ccj5fu.fsf@anie.imag.fr","threadId":"35022","inReplyTo":"20130925234121.GD9464@google.com","subject":"Re: What's cooking in git.git (Sep 2013, #08; Wed, 25)","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-09-26T09:30:29Z","receivedAt":"2013-09-26T09:30:29Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Jonathan Nieder <jrnieder@gmail.com> writes:\n\n> I'll probably be releasing 1.8.4.1 tomorrow.  If you have time to\n> experiment with \"maint\" or \"master\" to find any remaining problems\n> until then, that will be very welcome.\n\nIt seems mm/rebase-continue-freebsd-WB (99855dd) hasn't been merged to\nmaint. Right now, the *BSD folks have a broken \"git rebase\", I really\nthink this fix should go to maint.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"228327","messageId":"8BE13DA6F1DE41A5A17355D7F98D40D8@PhilipOakley","threadId":"35022","inReplyTo":"20130925234121.GD9464@google.com","subject":"Re: What's cooking in git.git (Sep 2013, #08; Wed, 25)","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2013-09-27T17:13:34Z","receivedAt":"2013-09-27T17:13:34Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Jonathan Nieder\" <jrnieder@gmail.com>\n> What's cooking in git.git (Sep 2013, #08; Wed, 25)\n\n>\n> * po/dot-url (2013-09-13) 2 commits\n>  (merged to 'next' on 2013-09-20 at 6a12786)\n> + config doc: update dot-repository notes\n> + doc: command line interface (cli) dot-repository dwimmery\n>\n> Explain how '.' can be used to refer to the \"current repository\"\n> in the documentation.\n>\n> Will merge to 'master'.\n>\nJonathan,\nDid you spot my recent \nhttp://thread.gmane.org/gmane.comp.version-control.git/235127?\n\nI'd been off ill, and away on business, so hadn't had much chance to \nproperly keep up.\n\nPhilip\n"},{"id":"228328","messageId":"20130927175258.GK9464@google.com","threadId":"35022","inReplyTo":"8BE13DA6F1DE41A5A17355D7F98D40D8@PhilipOakley","subject":"Re: What's cooking in git.git (Sep 2013, #08; Wed, 25)","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2013-09-27T17:52:58Z","receivedAt":"2013-09-27T17:52:58Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Philip Oakley wrote:\n\n> Jonathan,\n> Did you spot my recent\n> http://thread.gmane.org/gmane.comp.version-control.git/235127?\n\nWill take a look.  Thanks.\n"}]}