{"thread":{"id":"29877","subject":"[ANNOUNCE] Git 1.7.10-rc0","startedAt":"2012-03-08T01:35:07Z","lastAt":"2012-09-17T13:15:28Z","messageCount":22,"participants":["Junio C Hamano","Jeff King","Thomas Rast","Nguyen Thai Ngoc Duy","Jakub Narebski","Tim Henigan","Marc Branchaud","Ramkumar Ramachandra"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"186369","messageId":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":null,"subject":"[ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T01:35:07Z","receivedAt":"2012-03-08T01:35:07Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\nA release candidate Git 1.7.10-rc0 is now available for testing at\nthe usual places.\n\nThe release tarballs are found at:\n\n    http://code.google.com/p/git-core/downloads/list\n\nand their SHA-1 checksums are:\n\n96d1d25fd4f681246009b24fcaa4e41d88223f5b  git-1.7.10.rc0.tar.gz\na8c76f12980a287e0f6a0f285768ab492caaed98  git-htmldocs-1.7.10.rc0.tar.gz\n8f5f8aa4f692eb3d6e3549f6eb0fb0b5419c2f57  git-manpages-1.7.10.rc0.tar.gz\n\nAlso the following public repositories all have a copy of the v1.7.10.rc0\ntag and the master branch that the tag points at:\n\n  url = git://repo.or.cz/alt-git.git\n  url = https://code.google.com/p/git-core/\n  url = git://git.sourceforge.jp/gitroot/git-core/git.git\n  url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core\n  url = https://github.com/gitster/git\n\nThe other day, soon after announcement of the 1.7.9.3 maintenance\nrelease, there was a report that some tests did not pass on one\nplatform.  Even though it is better than not seeing one, such a late\nreport saddens us, especially because the exact test breakage has\nbeen in the master and next branches for quite some time for people\nto catch before it goes to any released versions.\n\nPlease test this and later pre-releases to make sure no such late\nreport has to come for the upcoming 1.7.10 final.\n\nThanks.\n\n\nGit v1.7.10 Release Notes (draft)\n=========================\n\nCompatibility Notes\n-------------------\n\n * From this release on, the \"git merge\" command in an interactive\n   session will start an editor when it automatically resolves the\n   merge for the user to explain the resulting commit, just like the\n   \"git commit\" command does when it wasn't given a commit message.\n\n   If you have a script that runs \"git merge\" and keeps its standard\n   input and output attached to the user's terminal, and if you do not\n   want the user to explain the resulting merge commits, you can\n   export GIT_MERGE_AUTOEDIT environment variable set to \"no\", like\n   this:\n\n\t#!/bin/sh\n\tGIT_MERGE_AUTOEDIT=no\n\texport GIT_MERGE_AUTOEDIT\n\n   to disable this behaviour (if you want your users to explain their\n   merge commits, you do not have to do anything).  Alternatively, you\n   can give the \"--no-edit\" option to individual invocations of the\n   \"git merge\" command if you know everybody who uses your script has\n   Git v1.7.8 or newer.\n\n\nUpdates since v1.7.9\n--------------------\n\nUI, Workflows & Features\n\n * Teams for localizing the messages from the Porcelain layer of\n   commands are starting to form, thanks to Jiang Xin who volunteered\n   to be the localization coordinator.  An initial set of translated\n   messages for simplified chinese is available.\n\n * The configuration mechanism learned an \"include\" facility; an\n   assignment to the include.path pseudo-variable causes the named\n   file to be included in-place when Git looks up configuration\n   variables.\n\n * A content filter (clean/smudge) used to be just a way to make the\n   recorded contents \"more useful\", and allowed to fail; a filter can\n   new optionally be marked as \"required\".\n\n * Options whose names begin with \"--no-\" (e.g. the \"--no-verify\"\n   option of the \"git commit\" command) can be negated by omitting\n   \"no-\" from its name, e.g. \"git commit --verify\".\n\n * \"git am\" learned to pass \"-b\" option to underlying \"git mailinfo\", so\n   that bracketed string other than \"PATCH\" at the beginning can be kept.\n\n * \"git clone\" learned \"--single-branch\" option to limit cloning to a\n   single branch (surprise!).\n\n * \"git clone\" learned to detach the HEAD in the resulting repository\n   when the source repository's HEAD does not point to a branch.\n\n * When showing a patch while ignoring whitespace changes, the context\n   lines are taken from the postimage, in order to make it easier to\n   view the output.\n\n * \"git diff --stat\" learned to adjust the width of the output on\n   wider terminals, and give more columns to pathnames as needed.\n\n * \"diff-highlight\" filter (in contrib/) was updated to produce more\n   aesthetically pleasing output.\n\n * \"fsck\" learned \"--no-dangling\" option to omit dangling object\n   information.\n\n * \"git log -G\" learned to pay attention to the \"-i\" option and can\n   find patch hunks that introduce or remove a string that matches the\n   given pattern ignoring the case.\n\n * \"git merge\" in an interactive session learned to spawn the editor\n   by default to let the user edit the auto-generated merge message,\n   to encourage people to explain their merges better. Legacy scripts\n   can export GIT_MERGE_AUTOEDIT=no to retain the historical behavior.\n   Both \"git merge\" and \"git pull\" can be given --no-edit from the\n   command line to accept the auto-generated merge message.\n\n * The advise message given when the user didn't give enough clue on\n   what to merge to \"git pull\" and \"git merge\" has been updated to\n   be more concise and easier to understand.\n\n * \"git push\" learned the \"--prune\" option, similar to \"git fetch\".\n\n * \"git symbolic-ref\" learned the \"--short\" option to abbreviate the\n   refname it shows unambiguously.\n\n * \"git tag --list\" can be given \"--points-at <object>\" to limit its\n   output to those that point at the given object.\n\n * \"gitweb\" allows intermediate entries in the directory hierarchy\n   that leads to a projects to be clicked, which in turn shows the\n   list of projects inside that directory.\n\n * \"gitweb\" learned to read various pieces of information for the\n   repositories lazily, instead of reading everything that could be\n   needed (including the ones that are not necessary for a specific\n   task).\n\n * Project search in \"gitweb\" shows the substring that matched in the\n   project name and description highlighted.\n\nForeign Interface\n\n * Improved handling of views, labels and branches in \"git-p4\" (in contrib).\n\n * \"git-p4\" (in contrib) suffered from unnecessary merge conflicts when\n   p4 expanded the embedded $RCS$-like keywords; it can be now told to\n   unexpand them.\n\n * Some \"git-svn\" updates.\n\n * \"vcs-svn\"/\"svn-fe\" learned to read dumps with svn-deltas and\n   support incremental imports.\n\n * \"git difftool/mergetool\" learned to drive DeltaWalker.\n\nPerformance\n\n * Unnecessary calls to parse_object() \"git upload-pack\" makes in\n   response to \"git fetch\", have been eliminated, to help performance\n   in repositories with excessive number of refs.\n\nInternal Implementation (please report possible regressions)\n\n * Recursive call chains in \"git index-pack\" to deal with long delta\n   chains have been flattened, to reduce the stack footprint.\n\n * Use of add_extra_ref() API is now gone, to make it possible to\n   cleanly restructure the overall refs API.\n\n * The command line parser of \"git pack-objects\" now uses parse-options\n   API.\n\n * The test suite supports the new \"test_pause\" helper function.\n\n * Parallel to the test suite, there is a beginning of performance\n   benchmarking framework.\n\n * t/Makefile is adjusted to prevent newer versions of GNU make from\n   running tests in seemingly random order.\n\n * The code to check if a path points at a file beyond a symbolic link\n   has been restructured to be thread-safe.\n\nAlso contains minor documentation updates and code clean-ups.\n\n\nFixes since v1.7.9\n------------------\n\nUnless otherwise noted, all the fixes since v1.7.9 in the maintenance\nreleases are contained in this release (see release notes to them for\ndetails).\n\n * \"git bundle\" did not record boundary commits correctly when there\n   are many of them.\n   (merge efe4be1 tr/maint-bundle-boundary later to maint).\n\n * \"git diff-index\" and its friends at the plumbing level showed the\n   \"diff --git\" header and nothing else for a path whose cached stat\n   info is dirty without actual difference when asked to produce a\n   patch. This was a longstanding bug that we could have fixed long\n   time ago.\n   (merge b3f01ff jc/maint-diff-patch-header later to maint).\n\n * The code to synthesize the fake ancestor tree used by 3-way merge\n   fallback in \"git am\" was not prepared to read a patch created with\n   a non-standard -p<num> value.\n   (merge a61ba26 jc/am-3-nonstandard-popt later to maint).\n\n * \"gitweb\" used to drop warnings in the log file when \"heads\" view is\n   accessed in a repository whose HEAD does not point at a valid\n   branch.\n"},{"id":"186378","messageId":"20120308063054.GD7643@sigill.intra.peff.net","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2012-03-08T06:30:54Z","receivedAt":"2012-03-08T06:30:54Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Mar 07, 2012 at 05:35:07PM -0800, Junio C Hamano wrote:\n\n>  * A content filter (clean/smudge) used to be just a way to make the\n>    recorded contents \"more useful\", and allowed to fail; a filter can\n>    new optionally be marked as \"required\".\n\ns/new/now/\n\n>  * \"git am\" learned to pass \"-b\" option to underlying \"git mailinfo\", so\n>    that bracketed string other than \"PATCH\" at the beginning can be kept.\n\ns/bracketed/a &/\n\n(or s/string/&s/)\n\n>  * \"git clone\" learned to detach the HEAD in the resulting repository\n>    when the source repository's HEAD does not point to a branch.\n\nHmm. Hasn't this been the case for a while? The jk/clone-detached topic\nwent into v1.7.7, and it was just fixes for some corner cases; actually\nwriting a detached HEAD is much older than that, even.\n\nI assume this entry is due to the nd/clone-detached topic. Reading over\nthose commits, it seems like it is more about properly checking the\n\"--branch\" argument for being detached, so we can handle\n\"--branch=v1.0\". So maybe:\n\n  * \"git clone\" learned to detach the HEAD in the resulting repository\n    when the user specifies a tag with \"--branch\" (e.g., \"--branch=v1.0\").\n    Clone also learned to print the usual \"detached HEAD\" advice in such\n    a case, similar to \"git checkout v1.0\".\n\n>  * \"git log -G\" learned to pay attention to the \"-i\" option and can\n>    find patch hunks that introduce or remove a string that matches the\n>    given pattern ignoring the case.\n\nThis didn't parse well for me. Also, it affects -S, too, doesn't it?\nMaybe:\n\n  * \"git log -G\" and \"git log -S\" learned to pay attention to the \"-i\"\n    option. When \"-i\" is given, their patterns will match\n    case-insensitively.\n\n>  * The advise message given when the user didn't give enough clue on\n>    what to merge to \"git pull\" and \"git merge\" has been updated to\n>    be more concise and easier to understand.\n\ns/advise/advice/\n\n-Peff\n"},{"id":"186380","messageId":"7vlinbfv9z.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"20120308063054.GD7643@sigill.intra.peff.net","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T06:42:48Z","receivedAt":"2012-03-08T06:42:48Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King <peff@peff.net> writes:\n\nThanks to all other points.\n\n>>  * \"git log -G\" learned to pay attention to the \"-i\" option and can\n>>    find patch hunks that introduce or remove a string that matches the\n>>    given pattern ignoring the case.\n>\n> This didn't parse well for me. Also, it affects -S, too, doesn't it?\n> Maybe:\n>\n>   * \"git log -G\" and \"git log -S\" learned to pay attention to the \"-i\"\n>     option. When \"-i\" is given, their patterns will match\n>     case-insensitively.\n\nI was torn about this item, and indeed my earlier draft read like\nyours but I removed \"-S\" as it felt it was more confusing than it\nwas worth.  The thing is that -S does not take any pattern --- it is\nmeant to be given a (typically a multi-line) block of text to find\nwhere the exact block cease to exist in the file.\n"},{"id":"186381","messageId":"7vk42vfv3c.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"20120308063054.GD7643@sigill.intra.peff.net","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T06:46:47Z","receivedAt":"2012-03-08T06:46:47Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King <peff@peff.net> writes:\n\nThanks to all other points.\n\n>>  * \"git log -G\" learned to pay attention to the \"-i\" option and can\n>>    find patch hunks that introduce or remove a string that matches the\n>>    given pattern ignoring the case.\n>\n> This didn't parse well for me. Also, it affects -S, too, doesn't it?\n> Maybe:\n>\n>   * \"git log -G\" and \"git log -S\" learned to pay attention to the \"-i\"\n>     option. When \"-i\" is given, their patterns will match\n>     case-insensitively.\n\nI was torn about this item, and indeed my earlier draft read like\nyours but I removed \"-S\" as it felt it was more confusing than it\nwas worth.  The thing is that -S does not take any pattern --- it is\nmeant to be given a (typically a multi-line) block of text to find\nwhere the exact block cease to exist in the file.\n\n * \"git log -G\" and \"git log -S\" learned to pay attention to the \"-i\"\n   option.  With \"-i\", \"log -G\" finds patch hunks that introduce or\n   remove a string that matches the given pattern ignoring the case.\n   Similarly with \"-i\", \"log -S\" finds where the given block of text\n   appears or disappears from the file, but this comparison is done\n   case-insensitively.\n"},{"id":"186382","messageId":"20120308065306.GA8799@sigill.intra.peff.net","threadId":"29877","inReplyTo":"7vk42vfv3c.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2012-03-08T06:53:06Z","receivedAt":"2012-03-08T06:53:06Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Mar 07, 2012 at 10:46:47PM -0800, Junio C Hamano wrote:\n\n> >   * \"git log -G\" and \"git log -S\" learned to pay attention to the \"-i\"\n> >     option. When \"-i\" is given, their patterns will match\n> >     case-insensitively.\n> \n> I was torn about this item, and indeed my earlier draft read like\n> yours but I removed \"-S\" as it felt it was more confusing than it\n> was worth.  The thing is that -S does not take any pattern --- it is\n> meant to be given a (typically a multi-line) block of text to find\n> where the exact block cease to exist in the file.\n\nYeah, though I think many people do treat it as a fixed-string pattern\n(I typically use \"git log -Sfoo\" to search for \"foo\", though perhaps\nthat is because I trained my fingers long before \"-G\" existed. \"-S\" is\nalso a lot faster).\n\nMy initial reaction to your statement was \"well, if we can't justify it\nin the release notes, then perhaps it is wrong for -S to be respecting\n-i\". But I don't think that is right. The code is doing the right thing,\nand it is merely that \"-S\" is a little-used and often-misunderstood\ntool, and you would naturally want to avoid mentioning it to avoid\ncomplicating the notes and confusing the reader.\n\n>  * \"git log -G\" and \"git log -S\" learned to pay attention to the \"-i\"\n>    option.  With \"-i\", \"log -G\" finds patch hunks that introduce or\n>    remove a string that matches the given pattern ignoring the case.\n>    Similarly with \"-i\", \"log -S\" finds where the given block of text\n>    appears or disappears from the file, but this comparison is done\n>    case-insensitively.\n\nI think that's much better.\n\nThough as a minor nit, the thing I had trouble parsing originally was\n\"...that matches the given pattern ignoring the case\". I think \"...ignores\nthe case when finding patch hunks that introduce...\" is a little easier\nto read.\n\n-Peff\n"},{"id":"186391","messageId":"14709b4345420da36a9152904bef4cc4503f78e4.1331196679.git.trast@student.ethz.ch","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"[PATCH 1/2] perf: load test-lib-functions from the correct directory","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2012-03-08T08:54:54Z","receivedAt":"2012-03-08T08:54:54Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Loading it in the subshells still referred to $TEST_DIRECTORY/..,\nwhich was only correct in preliminary versions of perf-lib.sh\n\nSigned-off-by: Thomas Rast <trast@student.ethz.ch>\n---\n\nThis and the next one fix two small bugs in the perf test suite.  They\ndon't affect anyone so far, which is why they went unnoticed.\n\n t/perf/p0000-perf-lib-sanity.sh |    5 +++++\n t/perf/perf-lib.sh              |    2 +-\n 2 files changed, 6 insertions(+), 1 deletion(-)\n\ndiff --git a/t/perf/p0000-perf-lib-sanity.sh b/t/perf/p0000-perf-lib-sanity.sh\nindex 2ca4aac..f8dd536 100755\n--- a/t/perf/p0000-perf-lib-sanity.sh\n+++ b/t/perf/p0000-perf-lib-sanity.sh\n@@ -38,4 +38,9 @@ test_expect_success 'test_export works with weird vars' '\n \ttest \"$bar\" = \"weird # variable\"\n '\n \n+test_perf 'test-lib-functions correctly loaded in subshells' '\n+\t: >a &&\n+\ttest_path_is_file a\n+'\n+\n test_done\ndiff --git a/t/perf/perf-lib.sh b/t/perf/perf-lib.sh\nindex 2a5e1f3..bcc0131 100644\n--- a/t/perf/perf-lib.sh\n+++ b/t/perf/perf-lib.sh\n@@ -119,7 +119,7 @@ test_run_perf_ () {\n \ttest_export_=\"test_cleanup\"\n \texport test_cleanup test_export_\n \t/usr/bin/time -f \"%E %U %S\" -o test_time.$i \"$SHELL\" -c '\n-. '\"$TEST_DIRECTORY\"/../test-lib-functions.sh'\n+. '\"$TEST_DIRECTORY\"/test-lib-functions.sh'\n test_export () {\n \t[ $# != 0 ] || return 0\n \ttest_export_=\"$test_export_\\\\|$1\"\n-- \n1.7.9.3.556.g7eb2d\n"},{"id":"186392","messageId":"1c5b174027fc70f084a6547352596d8c0305f6c9.1331196679.git.trast@student.ethz.ch","threadId":"29877","inReplyTo":"14709b4345420da36a9152904bef4cc4503f78e4.1331196679.git.trast@student.ethz.ch","subject":"[PATCH 2/2] perf: export some important test-lib variables","fromName":"Thomas Rast","fromEmail":"trast@student.ethz.ch","sentAt":"2012-03-08T08:54:55Z","receivedAt":"2012-03-08T08:54:55Z","isPatch":true,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"The only bug right now is that $GIT_TEST_CMP is needed for test_cmp to\nwork.\n\nHowever, we also export the three most important paths for tests:\n\n  TEST_DIRECTORY\n  TRASH_DIRECTORY\n  GIT_BUILD_DIR\n\nSince they are available within test_expect_success, a future test\nwriter may expect them to also be defined in test_perf.\n\nSigned-off-by: Thomas Rast <trast@student.ethz.ch>\n---\n t/perf/p0000-perf-lib-sanity.sh |   11 ++++++++++-\n t/perf/perf-lib.sh              |    4 ++++\n 2 files changed, 14 insertions(+), 1 deletion(-)\n\ndiff --git a/t/perf/p0000-perf-lib-sanity.sh b/t/perf/p0000-perf-lib-sanity.sh\nindex f8dd536..cf8e1ef 100755\n--- a/t/perf/p0000-perf-lib-sanity.sh\n+++ b/t/perf/p0000-perf-lib-sanity.sh\n@@ -38,9 +38,18 @@ test_expect_success 'test_export works with weird vars' '\n \ttest \"$bar\" = \"weird # variable\"\n '\n \n+test_perf 'important variables available in subshells' '\n+\ttest -n \"$HOME\" &&\n+\ttest -n \"$TEST_DIRECTORY\" &&\n+\ttest -n \"$TRASH_DIRECTORY\" &&\n+\ttest -n \"$GIT_BUILD_DIR\"\n+'\n+\n test_perf 'test-lib-functions correctly loaded in subshells' '\n \t: >a &&\n-\ttest_path_is_file a\n+\ttest_path_is_file a &&\n+\t: >b &&\n+\ttest_cmp a b\n '\n \n test_done\ndiff --git a/t/perf/perf-lib.sh b/t/perf/perf-lib.sh\nindex bcc0131..5580c22 100644\n--- a/t/perf/perf-lib.sh\n+++ b/t/perf/perf-lib.sh\n@@ -45,6 +45,10 @@ TEST_NO_CREATE_REPO=t\n \n . ../test-lib.sh\n \n+# Variables from test-lib that are normally internal to the tests; we\n+# need to export them for test_perf subshells\n+export TEST_DIRECTORY TRASH_DIRECTORY GIT_BUILD_DIR GIT_TEST_CMP\n+\n perf_results_dir=$TEST_OUTPUT_DIRECTORY/test-results\n mkdir -p \"$perf_results_dir\"\n rm -f \"$perf_results_dir\"/$(basename \"$0\" .sh).subtests\n-- \n1.7.9.3.556.g7eb2d\n"},{"id":"186404","messageId":"87y5rbpfap.fsf@thomas.inf.ethz.ch","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Thomas Rast","fromEmail":"trast@inf.ethz.ch","sentAt":"2012-03-08T10:17:50Z","receivedAt":"2012-03-08T10:17:50Z","isPatch":false,"sender":{"key":"tr@thomasrast.ch","avatar":"https://avatars.githubusercontent.com/u/153510?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n>  * Parallel to the test suite, there is a beginning of performance\n>    benchmarking framework.\n\nI just noticed that this does not work on OS X; its 'time' does not\nsupport the -f option.  For now I think I'm happy; it can compare\nseveral versions of Git on Linux to detect performance improvements or\nregressions.  Comparability across systems or platforms was never a main\ngoal.\n\nIn the long run we'll have to change it to either use 'time -p'\neverywhere and parse that into shape -- at least GNU and OS X agree on\nwhat POSIX specifies ;-) -- or just supply a small helper utility that\ndoes the timings for us in a ready-to-use format.\n\n-- \nThomas Rast\ntrast@{inf,student}.ethz.ch\n"},{"id":"186406","messageId":"CACsJy8CYTnrcAX6TNORdg=KAk4_xNupT11Uw8o8gnW6NtQtMCA@mail.gmail.com","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-03-08T10:29:16Z","receivedAt":"2012-03-08T10:29:16Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Thu, Mar 8, 2012 at 8:35 AM, Junio C Hamano <gitster@pobox.com> wrote:\n>  * \"git clone\" learned \"--single-branch\" option to limit cloning to a\n>   single branch (surprise!).\n\n--single-branch also limits fetching tags to minimum, I'm not sure we\nneed to mention that. It may be a good idea to mention \"shallow clone\"\nor --depth, where this feature is most beneficial, to catch people's\neyes if they are interested in shallow clone.\n-- \nDuy\n"},{"id":"186409","messageId":"m3wr6vs7a2.fsf@localhost.localdomain","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2012-03-08T10:42:49Z","receivedAt":"2012-03-08T10:42:49Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Junio C Hamano <gitster@pobox.com> writes:\n\n> Updates since v1.7.9\n> --------------------\n> \n> UI, Workflows & Features\n[...]\n>  * \"gitweb\" allows intermediate entries in the directory hierarchy\n>    that leads to a projects to be clicked, which in turn shows the\n>    list of projects inside that directory.\n> \n>  * \"gitweb\" learned to read various pieces of information for the\n>    repositories lazily, instead of reading everything that could be\n>    needed (including the ones that are not necessary for a specific\n>    task).\n> \n>  * Project search in \"gitweb\" shows the substring that matched in the\n>    project name and description highlighted.\n\n\n[...]\n> Fixes since v1.7.9\n> ------------------\n> \n> Unless otherwise noted, all the fixes since v1.7.9 in the maintenance\n> releases are contained in this release (see release notes to them for\n> details).\n[...]\n\n>  * \"gitweb\" used to drop warnings in the log file when \"heads\" view is\n>    accessed in a repository whose HEAD does not point at a valid\n>    branch.\n\nIt looks like fix for fixed-string project search is missing.\n\nNb. I don't know if it is worth mentioning, and if it should be in\n\"Fixes\" or \"Updates\", but gitweb now supports utf-8 search, anc checks\nregular expression for validity before using it in search.\n\n-- \nJakub Narebski\n"},{"id":"186444","messageId":"CAFouetgY+HSFksZkOGHcD41kHwfedtta0XoDemwyfQKOiJM1RA@mail.gmail.com","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Tim Henigan","fromEmail":"tim.henigan@gmail.com","sentAt":"2012-03-08T13:18:48Z","receivedAt":"2012-03-08T13:18:48Z","isPatch":false,"sender":{"key":"tim.henigan@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42022?v=4"},"body":"On Wed, Mar 7, 2012 at 8:35 PM, Junio C Hamano <gitster@pobox.com> wrote:\n>\n> Updates since v1.7.9\n> --------------------\n>\n> UI, Workflows & Features\n\nAre additions to contrib/ normally mentioned here?  If so, this the\nfirst release to include \"git diffall\" (commit 1252bbe1c685).\n"},{"id":"186454","messageId":"4F58CD8F.8030004@xiplink.com","threadId":"29877","inReplyTo":"7v7gyvkh84.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Marc Branchaud","fromEmail":"marcnarc@xiplink.com","sentAt":"2012-03-08T15:17:35Z","receivedAt":"2012-03-08T15:17:35Z","isPatch":false,"sender":{"key":"marcnarc@xiplink.com","avatar":"https://avatars.githubusercontent.com/u/14980203?v=4"},"body":"On 12-03-07 08:35 PM, Junio C Hamano wrote:\n>\n\n[ snip ]\n\n>\n>   * \"gitweb\" allows intermediate entries in the directory hierarchy\n>     that leads to a projects to be clicked, which in turn shows the\n\ns/projects/project/\n\n>     list of projects inside that directory.\n\n\t\tM.\n"},{"id":"186462","messageId":"7v4ntzf45w.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"m3wr6vs7a2.fsf@localhost.localdomain","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T16:28:27Z","receivedAt":"2012-03-08T16:28:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jakub Narebski <jnareb@gmail.com> writes:\n\n> Junio C Hamano <gitster@pobox.com> writes:\n> ...\n>> Fixes since v1.7.9\n>> ------------------\n>> \n>> Unless otherwise noted, all the fixes since v1.7.9 in the maintenance\n>> releases are contained in this release (see release notes to them for\n>> details).\n> [...]\n>\n>>  * \"gitweb\" used to drop warnings in the log file when \"heads\" view is\n>>    accessed in a repository whose HEAD does not point at a valid\n>>    branch.\n>\n> It looks like fix for fixed-string project search is missing.\n\nHasn't it been already fixed in the 1.7.9.x maintenance track?\n"},{"id":"186464","messageId":"201203081756.00604.jnareb@gmail.com","threadId":"29877","inReplyTo":"7v4ntzf45w.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2012-03-08T16:55:59Z","receivedAt":"2012-03-08T16:55:59Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Junio C Hamano wrote:\n> Jakub Narebski <jnareb@gmail.com> writes:\n> > Junio C Hamano <gitster@pobox.com> writes:\n> > ...\n> >> Fixes since v1.7.9\n> >> ------------------\n> >> \n> >> Unless otherwise noted, all the fixes since v1.7.9 in the maintenance\n> >> releases are contained in this release (see release notes to them for\n> >> details).\n> > [...]\n> >\n> >>  * \"gitweb\" used to drop warnings in the log file when \"heads\" view is\n> >>    accessed in a repository whose HEAD does not point at a valid\n> >>    branch.\n> >\n> > It looks like fix for fixed-string project search is missing.\n> \n> Hasn't it been already fixed in the 1.7.9.x maintenance track?\n\nI don't see it either in 'maint' or in 'master'.\n\nIt is surely not in master, otherwise 'stg rebase' would drop the\n\"gitweb: Fix fixed string (non-regexp) project search\" patch.\n\n-- \nJakub Narebski\nPoland\n"},{"id":"186484","messageId":"7vpqcmdg0t.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"CACsJy8CYTnrcAX6TNORdg=KAk4_xNupT11Uw8o8gnW6NtQtMCA@mail.gmail.com","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T19:55:14Z","receivedAt":"2012-03-08T19:55:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:\n\n> On Thu, Mar 8, 2012 at 8:35 AM, Junio C Hamano <gitster@pobox.com> wrote:\n>>  * \"git clone\" learned \"--single-branch\" option to limit cloning to a\n>>   single branch (surprise!).\n>\n> --single-branch also limits fetching tags to minimum, I'm not sure we\n> need to mention that.\n\nYeah, I was of two minds when I wrote it. It is obvious once you\nthink about it, but spelling it out does not cost much, so let's do\nthis.\n\n * \"git clone\" learned \"--single-branch\" option to limit cloning to a\n   single branch (surprise!); tags that do not point into the history\n   of the branch are not fetched.\n\nThanks.\n"},{"id":"186485","messageId":"7vlinadg05.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"20120308065306.GA8799@sigill.intra.peff.net","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T19:55:38Z","receivedAt":"2012-03-08T19:55:38Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King <peff@peff.net> writes:\n\n> Though as a minor nit, the thing I had trouble parsing originally was\n> \"...that matches the given pattern ignoring the case\". I think \"...ignores\n> the case when finding patch hunks that introduce...\" is a little easier\n> to read.\n\nThanks, will do.\n"},{"id":"186486","messageId":"7vhaxydfjq.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"201203081756.00604.jnareb@gmail.com","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T20:05:29Z","receivedAt":"2012-03-08T20:05:29Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jakub Narebski <jnareb@gmail.com> writes:\n\n> I don't see it either in 'maint' or in 'master'.\n>\n> It is surely not in master, otherwise 'stg rebase' would drop the\n> \"gitweb: Fix fixed string (non-regexp) project search\" patch.\n\nThat is because some of the topics were still very new to 'next' and\nI didn't want to disrupt the zeroth release candidates with them.  I\nthink the following topics should be on 'master' before -rc1:\n\n + vr/branch-doc                                                03-06/03-06    #3\n + jn/maint-do-not-match-with-unsanitized-searchtext            03-06/03-06    #1\n + jl/maint-submodule-relative                                  03-04/03-07    #4\n\nThe two dates are the day the last patch in the series hit my tree,\nand the day the topic as a whole has become part of next, and #<num>\nshows the number of patches in the series (you can run \"cook -w -\"\nand feed the \"What's cooking\" message into its standard input to get\nthe summary; both are available in the 'todo' branch).\n"},{"id":"186487","messageId":"7v8vjadfgg.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"CAFouetgY+HSFksZkOGHcD41kHwfedtta0XoDemwyfQKOiJM1RA@mail.gmail.com","subject":"Re: [ANNOUNCE] Git 1.7.10-rc0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-08T20:07:27Z","receivedAt":"2012-03-08T20:07:27Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Tim Henigan <tim.henigan@gmail.com> writes:\n\n> On Wed, Mar 7, 2012 at 8:35 PM, Junio C Hamano <gitster@pobox.com> wrote:\n>>\n>> Updates since v1.7.9\n>> --------------------\n>>\n>> UI, Workflows & Features\n>\n> Are additions to contrib/ normally mentioned here?\n\nUsually not.  You could send a patch whose addition does not exceed\nthree lines if you want, though.\n"},{"id":"186563","messageId":"1331300127-21169-1-git-send-email-tim.henigan@gmail.com","threadId":"29877","inReplyTo":"7v8vjadfgg.fsf@alter.siamese.dyndns.org","subject":"[PATCH] RelNotes: noted the addition of contrib/diffall","fromName":"Tim Henigan","fromEmail":"tim.henigan@gmail.com","sentAt":"2012-03-09T13:35:27Z","receivedAt":"2012-03-09T13:35:27Z","isPatch":true,"sender":{"key":"tim.henigan@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42022?v=4"},"body":"Signed-off-by: Tim Henigan <tim.henigan@gmail.com>\n---\n\nI wasn't sure if you wanted an actual patch or just wanted me to write\nup the paragraph.  If you squash this in to some other commit, that is\nfine with me.\n\n\n Documentation/RelNotes/1.7.10.txt |    3 +++\n 1 file changed, 3 insertions(+)\n\ndiff --git a/Documentation/RelNotes/1.7.10.txt b/Documentation/RelNotes/1.7.10.txt\nindex ae446e0..60722e2 100644\n--- a/Documentation/RelNotes/1.7.10.txt\n+++ b/Documentation/RelNotes/1.7.10.txt\n@@ -106,6 +106,9 @@ UI, Workflows & Features\n  * Project search in \"gitweb\" shows the substring that matched in the\n    project name and description highlighted.\n \n+ * \"git diffall\" can now be installed from contrib/. The script drives\n+   an external tool to perform a directory diff of two Git revisions.\n+\n Foreign Interface\n \n  * Improved handling of views, labels and branches in \"git-p4\" (in contrib).\n-- \n1.7.10.rc0\n"},{"id":"186575","messageId":"7v399h7i96.fsf@alter.siamese.dyndns.org","threadId":"29877","inReplyTo":"1331300127-21169-1-git-send-email-tim.henigan@gmail.com","subject":"Re: [PATCH] RelNotes: noted the addition of contrib/diffall","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2012-03-09T18:15:49Z","receivedAt":"2012-03-09T18:15:49Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Tim Henigan <tim.henigan@gmail.com> writes:\n\n> I wasn't sure if you wanted an actual patch or just wanted me to write\n> up the paragraph.  If you squash this in to some other commit, that is\n> fine with me.\n\nI didn't mean to burden you with a proper patch submission and just\na paragraph write-up was perfectly fine.\n\n> + * \"git diffall\" can now be installed from contrib/. The script drives\n> +   an external tool to perform a directory diff of two Git revisions.\n\nI'm tempted to add a third line, like this:\n\n   ... an external tool to perform a directory diff of two Git revisions\n   in one go, unlike \"difftool\" which compares one-file-at-a-time.\n\nto make the true value of this new addition stand out.\n\nThanks.\n"},{"id":"186578","messageId":"CAFouetg7rZ3F6iUgXbHX0kDCo0kje4yx8T0sfHseXxDnJosbAw@mail.gmail.com","threadId":"29877","inReplyTo":"7v399h7i96.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] RelNotes: noted the addition of contrib/diffall","fromName":"Tim Henigan","fromEmail":"tim.henigan@gmail.com","sentAt":"2012-03-09T18:41:57Z","receivedAt":"2012-03-09T18:41:57Z","isPatch":true,"sender":{"key":"tim.henigan@gmail.com","avatar":"https://avatars.githubusercontent.com/u/42022?v=4"},"body":"On Fri, Mar 9, 2012 at 1:15 PM, Junio C Hamano <gitster@pobox.com> wrote:\n> Tim Henigan <tim.henigan@gmail.com> writes:\n>\n>> + * \"git diffall\" can now be installed from contrib/. The script drives\n>> +   an external tool to perform a directory diff of two Git revisions.\n>\n> I'm tempted to add a third line, like this:\n>\n>   ... an external tool to perform a directory diff of two Git revisions\n>   in one go, unlike \"difftool\" which compares one-file-at-a-time.\n>\n> to make the true value of this new addition stand out.\n\nI like the added third line, but would remove the dashes in\n\"one-file-at-a-time\".\n\nThanks,\nTim\n"},{"id":"199225","messageId":"CALkWK0=1_2RfR5_xzjKANEB-DjdGhZ9dVZqwRwaWdSmRqg6X9g@mail.gmail.com","threadId":"29877","inReplyTo":"1c5b174027fc70f084a6547352596d8c0305f6c9.1331196679.git.trast@student.ethz.ch","subject":"Re: [PATCH 2/2] perf: export some important test-lib variables","fromName":"Ramkumar Ramachandra","fromEmail":"artagnon@gmail.com","sentAt":"2012-09-17T13:15:28Z","receivedAt":"2012-09-17T13:15:28Z","isPatch":true,"sender":{"key":"r@artagnon.com","avatar":"https://avatars.githubusercontent.com/u/37226?v=4"},"body":"Hi Thomas,\n\nThomas Rast wrote:\n> The only bug right now is that $GIT_TEST_CMP is needed for test_cmp to\n> work.\n\nWhat bug?  You're exporting it, right?\n\n>  test_perf 'test-lib-functions correctly loaded in subshells' '\n>         : >a &&\n> -       test_path_is_file a\n> +       test_path_is_file a &&\n> +       : >b &&\n> +       test_cmp a b\n>  '\n\nThis test fails, presumably because of test_cmp.\n\nRam\n"}]}