{"thread":{"id":"21187","subject":"[ANNOUNCE] GIT 1.6.5","startedAt":"2009-10-11T08:40:29Z","lastAt":"2009-10-21T21:21:35Z","messageCount":18,"participants":["Junio C Hamano","Steven Noonan","Jakub Narebski","Sebastian Pipping","Miklos Vajna","Nanako Shiraishi","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"124591","messageId":"7v8wfi1fya.fsf@alter.siamese.dyndns.org","threadId":"21187","inReplyTo":null,"subject":"[ANNOUNCE] GIT 1.6.5","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-10-11T08:40:29Z","receivedAt":"2009-10-11T08:40:29Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"The latest feature release GIT 1.6.5 is available at the usual\nplaces:\n\n http://www.kernel.org/pub/software/scm/git/\n\n git-1.6.5.tar.{gz,bz2}\t\t\t(source tarball)\n git-htmldocs-1.6.5.tar.{gz,bz2}\t\t(preformatted docs)\n git-manpages-1.6.5.tar.{gz,bz2}\t\t(preformatted docs)\n\nThe RPM binary packages for a few architectures are found in:\n\n RPMS/$arch/git-*-1.6.5-1.fc9.$arch.rpm\t(RPM)\n\nThis cycle took a bit longer than I hoped, but here it is. We already\nhave some new features cooking in 'next', and I expect we may be able to\nhave 1.6.6 by the end of the year.\n\nEnjoy.\n\n----------------------------------------------------------------\n\nGIT v1.6.5 Release Notes\n========================\n\nIn git 1.7.0, which was planned to be the release after 1.6.5, \"git\npush\" into a branch that is currently checked out will be refused by\ndefault.\n\nYou can choose what should happen upon such a push by setting the\nconfiguration variable receive.denyCurrentBranch in the receiving\nrepository.\n\nAlso, \"git push $there :$killed\" to delete the branch $killed in a remote\nrepository $there, when $killed branch is the current branch pointed at by\nits HEAD, will be refused by default.\n\nYou can choose what should happen upon such a push by setting the\nconfiguration variable receive.denyDeleteCurrent in the receiving\nrepository.\n\nTo ease the transition plan, the receiving repository of such a\npush running this release will issue a big warning when the\nconfiguration variable is missing. Please refer to:\n\n http://git.or.cz/gitwiki/GitFaq#non-bare\n http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n\nfor more details on the reason why this change is needed and the\ntransition plan.\n\nUpdates since v1.6.4\n--------------------\n\n(subsystems)\n\n * various updates to gitk, git-svn and gitweb.\n\n(portability)\n\n * more improvements on mingw port.\n\n * mingw will also give FRSX as the default value for the LESS\n environment variable when the user does not have one.\n\n * initial support to compile git on Windows with MSVC.\n\n(performance)\n\n * On major platforms, the system can be compiled to use with Linus's\n block-sha1 implementation of the SHA-1 hash algorithm, which\n outperforms the default fallback implementation we borrowed from\n Mozilla.\n\n * Unnecessary inefficiency in deepening of a shallow repository has\n been removed.\n\n * \"git clone\" does not grab objects that it does not need (i.e.\n referenced only from refs outside refs/heads and refs/tags\n hierarchy) anymore.\n\n * The \"git\" main binary used to link with libcurl, which then dragged\n in a large number of external libraries. When using basic plumbing\n commands in scripts, this unnecessarily slowed things down. We now\n implement http/https/ftp transfer as a separate executable as we\n used to.\n\n * \"git clone\" run locally hardlinks or copies the files in .git/ to\n newly created repository. It used to give new mtime to copied files,\n but this delayed garbage collection to trigger unnecessarily in the\n cloned repository. We now preserve mtime for these files to avoid\n this issue.\n\n(usability, bells and whistles)\n\n * Human writable date format to various options, e.g. --since=yesterday,\n master@{2000.09.17}, are taught to infer some omitted input properly.\n\n * A few programs gave verbose \"advice\" messages to help uninitiated\n people when issuing error messages. An infrastructure to allow\n users to squelch them has been introduced, and a few such messages\n can be silenced now.\n\n * refs/replace/ hierarchy is designed to be usable as a replacement\n of the \"grafts\" mechanism, with the added advantage that it can be\n transferred across repositories.\n\n * \"git am\" learned to optionally ignore whitespace differences.\n\n * \"git am\" handles input e-mail files that has CRLF line endings sensibly.\n\n * \"git am\" learned \"--scissors\" option to allow you to discard early part\n of an incoming e-mail.\n\n * \"git archive -o output.zip\" works without being told what format to\n use with an explicit \"--format=zip\".option.\n\n * \"git checkout\", \"git reset\" and \"git stash\" learned to pick and\n choose to use selected changes you made, similar to \"git add -p\".\n\n * \"git clone\" learned a \"-b\" option to pick a HEAD to check out\n different from the remote's default branch.\n\n * \"git clone\" learned --recursive option.\n\n * \"git clone\" from a local repository on a different filesystem used to\n copy individual object files without preserving the old timestamp, giving\n them extra lifetime in the new repository until they gc'ed.\n\n * \"git commit --dry-run $args\" is a new recommended way to ask \"what would\n happen if I try to commit with these arguments.\"\n\n * \"git commit --dry-run\" and \"git status\" shows conflicted paths in a\n separate section to make them easier to spot during a merge.\n\n * \"git cvsimport\" now supports password-protected pserver access even\n when the password is not taken from ~/.cvspass file.\n\n * \"git fast-export\" learned --no-data option that can be useful when\n reordering commits and trees without touching the contents of\n blobs.\n\n * \"git fast-import\" has a pair of new front-end in contrib/ area.\n\n * \"git init\" learned to mkdir/chdir into a directory when given an\n extra argument (i.e. \"git init this\").\n\n * \"git instaweb\" optionally can use mongoose as the web server.\n\n * \"git log --decorate\" can optionally be told with --decorate=full to\n give the reference name in full.\n\n * \"git merge\" issued an unnecessarily scary message when it detected\n that the merge may have to touch the path that the user has local\n uncommitted changes to. The message has been reworded to make it\n clear that the command aborted, without doing any harm.\n\n * \"git push\" can be told to be --quiet.\n\n * \"git push\" pays attention to url.$base.pushInsteadOf and uses a URL\n that is derived from the URL used for fetching.\n\n * informational output from \"git reset\" that lists the locally modified\n paths is made consistent with that of \"git checkout $another_branch\".\n\n * \"git submodule\" learned to give submodule name to scripts run with\n \"foreach\" subcommand.\n\n * various subcommands to \"git submodule\" learned --recursive option.\n\n * \"git submodule summary\" learned --files option to compare the work\n tree vs the commit bound at submodule path, instead of comparing\n the index.\n\n * \"git upload-pack\", which is the server side support for \"git clone\" and\n \"git fetch\", can call a new post-upload-pack hook for statistics purposes.\n\n(developers)\n\n * With GIT_TEST_OPTS=\"--root=/p/a/t/h\", tests can be run outside the\n source directory; using tmpfs may give faster turnaround.\n\n * With NO_PERL_MAKEMAKER set, DESTDIR= is now honoured, so you can\n build for one location, and install into another location to tar it\n up.\n\nFixes since v1.6.4\n------------------\n\nAll of the fixes in v1.6.4.X maintenance series are included in this\nrelease, unless otherwise noted.\n"},{"id":"124621","messageId":"f488382f0910110930u1af92299ld5d72dbb31ed1914@mail.gmail.com","threadId":"21187","inReplyTo":"7v8wfi1fya.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] GIT 1.6.5","fromName":"Steven Noonan","fromEmail":"steven@uplinklabs.net","sentAt":"2009-10-11T16:30:13Z","receivedAt":"2009-10-11T16:30:13Z","isPatch":false,"sender":{"key":"steven@uplinklabs.net","avatar":"https://gravatar.com/avatar/b0cd397a10638433f76e084531aa0af3bef85f8fdb59b1ebe2ddaf168cd100e9?d=mp&s=160"},"body":"Uh-oh.\n\nAlcarin:crisscross steven$ git remote update\nUpdating origin\nfatal: 'git@github.com/tycho/crisscross.git' does not appear to be a\ngit repository\nfatal: The remote end hung up unexpectedly\nerror: Could not fetch origin\n\nAlcarin:crisscross steven$ nano -w .git/config\nAlcarin:crisscross steven$ git remote update\nUpdating origin\n\nThe 'ssh://' part is omitted in numerous places on github.com. I\nrealize github.com isn't the final authority on the syntax of the URI,\nbut was this an intentional change or a regression?\n\n- Steven\n\nOn Sun, Oct 11, 2009 at 1:40 AM, Junio C Hamano wrote:\n> The latest feature release GIT 1.6.5 is available at the usual\n> places:\n>\n>  http://www.kernel.org/pub/software/scm/git/\n>\n>  git-1.6.5.tar.{gz,bz2}                        (source tarball)\n>  git-htmldocs-1.6.5.tar.{gz,bz2}               (preformatted docs)\n>  git-manpages-1.6.5.tar.{gz,bz2}               (preformatted docs)\n>\n> The RPM binary packages for a few architectures are found in:\n>\n>  RPMS/$arch/git-*-1.6.5-1.fc9.$arch.rpm        (RPM)\n>\n> This cycle took a bit longer than I hoped, but here it is.  We already\n> have some new features cooking in 'next', and I expect we may be able to\n> have 1.6.6 by the end of the year.\n>\n> Enjoy.\n>\n> ----------------------------------------------------------------\n>\n> GIT v1.6.5 Release Notes\n> ========================\n>\n> In git 1.7.0, which was planned to be the release after 1.6.5, \"git\n> push\" into a branch that is currently checked out will be refused by\n> default.\n>\n> You can choose what should happen upon such a push by setting the\n> configuration variable receive.denyCurrentBranch in the receiving\n> repository.\n>\n> Also, \"git push $there :$killed\" to delete the branch $killed in a remote\n> repository $there, when $killed branch is the current branch pointed at by\n> its HEAD, will be refused by default.\n>\n> You can choose what should happen upon such a push by setting the\n> configuration variable receive.denyDeleteCurrent in the receiving\n> repository.\n>\n> To ease the transition plan, the receiving repository of such a\n> push running this release will issue a big warning when the\n> configuration variable is missing.  Please refer to:\n>\n>  http://git.or.cz/gitwiki/GitFaq#non-bare\n>  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n>\n> for more details on the reason why this change is needed and the\n> transition plan.\n>\n> Updates since v1.6.4\n> --------------------\n>\n> (subsystems)\n>\n>  * various updates to gitk, git-svn and gitweb.\n>\n> (portability)\n>\n>  * more improvements on mingw port.\n>\n>  * mingw will also give FRSX as the default value for the LESS\n>   environment variable when the user does not have one.\n>\n>  * initial support to compile git on Windows with MSVC.\n>\n> (performance)\n>\n>  * On major platforms, the system can be compiled to use with Linus's\n>   block-sha1 implementation of the SHA-1 hash algorithm, which\n>   outperforms the default fallback implementation we borrowed from\n>   Mozilla.\n>\n>  * Unnecessary inefficiency in deepening of a shallow repository has\n>   been removed.\n>\n>  * \"git clone\" does not grab objects that it does not need (i.e.\n>   referenced only from refs outside refs/heads and refs/tags\n>   hierarchy) anymore.\n>\n>  * The \"git\" main binary used to link with libcurl, which then dragged\n>   in a large number of external libraries.  When using basic plumbing\n>   commands in scripts, this unnecessarily slowed things down.  We now\n>   implement http/https/ftp transfer as a separate executable as we\n>   used to.\n>\n>  * \"git clone\" run locally hardlinks or copies the files in .git/ to\n>   newly created repository.  It used to give new mtime to copied files,\n>   but this delayed garbage collection to trigger unnecessarily in the\n>   cloned repository.  We now preserve mtime for these files to avoid\n>   this issue.\n>\n> (usability, bells and whistles)\n>\n>  * Human writable date format to various options, e.g. --since=yesterday,\n>   master@{2000.09.17}, are taught to infer some omitted input properly.\n>\n>  * A few programs gave verbose \"advice\" messages to help uninitiated\n>   people when issuing error messages.  An infrastructure to allow\n>   users to squelch them has been introduced, and a few such messages\n>   can be silenced now.\n>\n>  * refs/replace/ hierarchy is designed to be usable as a replacement\n>   of the \"grafts\" mechanism, with the added advantage that it can be\n>   transferred across repositories.\n>\n>  * \"git am\" learned to optionally ignore whitespace differences.\n>\n>  * \"git am\" handles input e-mail files that has CRLF line endings sensibly.\n>\n>  * \"git am\" learned \"--scissors\" option to allow you to discard early part\n>   of an incoming e-mail.\n>\n>  * \"git archive -o output.zip\" works without being told what format to\n>   use with an explicit \"--format=zip\".option.\n>\n>  * \"git checkout\", \"git reset\" and \"git stash\" learned to pick and\n>   choose to use selected changes you made, similar to \"git add -p\".\n>\n>  * \"git clone\" learned a \"-b\" option to pick a HEAD to check out\n>   different from the remote's default branch.\n>\n>  * \"git clone\" learned --recursive option.\n>\n>  * \"git clone\" from a local repository on a different filesystem used to\n>   copy individual object files without preserving the old timestamp, giving\n>   them extra lifetime in the new repository until they gc'ed.\n>\n>  * \"git commit --dry-run $args\" is a new recommended way to ask \"what would\n>   happen if I try to commit with these arguments.\"\n>\n>  * \"git commit --dry-run\" and \"git status\" shows conflicted paths in a\n>   separate section to make them easier to spot during a merge.\n>\n>  * \"git cvsimport\" now supports password-protected pserver access even\n>   when the password is not taken from ~/.cvspass file.\n>\n>  * \"git fast-export\" learned --no-data option that can be useful when\n>   reordering commits and trees without touching the contents of\n>   blobs.\n>\n>  * \"git fast-import\" has a pair of new front-end in contrib/ area.\n>\n>  * \"git init\" learned to mkdir/chdir into a directory when given an\n>   extra argument (i.e. \"git init this\").\n>\n>  * \"git instaweb\" optionally can use mongoose as the web server.\n>\n>  * \"git log --decorate\" can optionally be told with --decorate=full to\n>   give the reference name in full.\n>\n>  * \"git merge\" issued an unnecessarily scary message when it detected\n>   that the merge may have to touch the path that the user has local\n>   uncommitted changes to. The message has been reworded to make it\n>   clear that the command aborted, without doing any harm.\n>\n>  * \"git push\" can be told to be --quiet.\n>\n>  * \"git push\" pays attention to url.$base.pushInsteadOf and uses a URL\n>   that is derived from the URL used for fetching.\n>\n>  * informational output from \"git reset\" that lists the locally modified\n>   paths is made consistent with that of \"git checkout $another_branch\".\n>\n>  * \"git submodule\" learned to give submodule name to scripts run with\n>   \"foreach\" subcommand.\n>\n>  * various subcommands to \"git submodule\" learned --recursive option.\n>\n>  * \"git submodule summary\" learned --files option to compare the work\n>   tree vs the commit bound at submodule path, instead of comparing\n>   the index.\n>\n>  * \"git upload-pack\", which is the server side support for \"git clone\" and\n>   \"git fetch\", can call a new post-upload-pack hook for statistics purposes.\n>\n> (developers)\n>\n>  * With GIT_TEST_OPTS=\"--root=/p/a/t/h\", tests can be run outside the\n>   source directory; using tmpfs may give faster turnaround.\n>\n>  * With NO_PERL_MAKEMAKER set, DESTDIR= is now honoured, so you can\n>   build for one location, and install into another location to tar it\n>   up.\n>\n> Fixes since v1.6.4\n> ------------------\n>\n> All of the fixes in v1.6.4.X maintenance series are included in this\n> release, unless otherwise noted.\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n"},{"id":"124620","messageId":"f488382f0910110930k67b34da7p4a744d47073a948b@mail.gmail.com","threadId":"21187","inReplyTo":"f488382f0910110930u1af92299ld5d72dbb31ed1914@mail.gmail.com","subject":"Re: [ANNOUNCE] GIT 1.6.5","fromName":"Steven Noonan","fromEmail":"steven@uplinklabs.net","sentAt":"2009-10-11T16:30:47Z","receivedAt":"2009-10-11T16:30:47Z","isPatch":false,"sender":{"key":"steven@uplinklabs.net","avatar":"https://gravatar.com/avatar/b0cd397a10638433f76e084531aa0af3bef85f8fdb59b1ebe2ddaf168cd100e9?d=mp&s=160"},"body":"On Sun, Oct 11, 2009 at 9:30 AM, Steven Noonan wrote:\n> Uh-oh.\n>\n> Alcarin:crisscross steven$ git remote update\n> Updating origin\n> fatal: 'git@github.com/tycho/crisscross.git' does not appear to be a\n> git repository\n> fatal: The remote end hung up unexpectedly\n> error: Could not fetch origin\n>\n> Alcarin:crisscross steven$ nano -w .git/config\n> Alcarin:crisscross steven$ git remote update\n> Updating origin\n\nEr, meant to say before this that I edited the URI to include the\n'ssh://' and then it worked fine.\n\n>\n> The 'ssh://' part is omitted in numerous places on github.com. I\n> realize github.com isn't the final authority on the syntax of the URI,\n> but was this an intentional change or a regression?\n>\n> - Steven\n>\n> On Sun, Oct 11, 2009 at 1:40 AM, Junio C Hamano wrote:\n>> The latest feature release GIT 1.6.5 is available at the usual\n>> places:\n>>\n>>  http://www.kernel.org/pub/software/scm/git/\n>>\n>>  git-1.6.5.tar.{gz,bz2}                        (source tarball)\n>>  git-htmldocs-1.6.5.tar.{gz,bz2}               (preformatted docs)\n>>  git-manpages-1.6.5.tar.{gz,bz2}               (preformatted docs)\n>>\n>> The RPM binary packages for a few architectures are found in:\n>>\n>>  RPMS/$arch/git-*-1.6.5-1.fc9.$arch.rpm        (RPM)\n>>\n>> This cycle took a bit longer than I hoped, but here it is.  We already\n>> have some new features cooking in 'next', and I expect we may be able to\n>> have 1.6.6 by the end of the year.\n>>\n>> Enjoy.\n>>\n>> ----------------------------------------------------------------\n>>\n>> GIT v1.6.5 Release Notes\n>> ========================\n>>\n>> In git 1.7.0, which was planned to be the release after 1.6.5, \"git\n>> push\" into a branch that is currently checked out will be refused by\n>> default.\n>>\n>> You can choose what should happen upon such a push by setting the\n>> configuration variable receive.denyCurrentBranch in the receiving\n>> repository.\n>>\n>> Also, \"git push $there :$killed\" to delete the branch $killed in a remote\n>> repository $there, when $killed branch is the current branch pointed at by\n>> its HEAD, will be refused by default.\n>>\n>> You can choose what should happen upon such a push by setting the\n>> configuration variable receive.denyDeleteCurrent in the receiving\n>> repository.\n>>\n>> To ease the transition plan, the receiving repository of such a\n>> push running this release will issue a big warning when the\n>> configuration variable is missing.  Please refer to:\n>>\n>>  http://git.or.cz/gitwiki/GitFaq#non-bare\n>>  http://thread.gmane.org/gmane.comp.version-control.git/107758/focus=108007\n>>\n>> for more details on the reason why this change is needed and the\n>> transition plan.\n>>\n>> Updates since v1.6.4\n>> --------------------\n>>\n>> (subsystems)\n>>\n>>  * various updates to gitk, git-svn and gitweb.\n>>\n>> (portability)\n>>\n>>  * more improvements on mingw port.\n>>\n>>  * mingw will also give FRSX as the default value for the LESS\n>>   environment variable when the user does not have one.\n>>\n>>  * initial support to compile git on Windows with MSVC.\n>>\n>> (performance)\n>>\n>>  * On major platforms, the system can be compiled to use with Linus's\n>>   block-sha1 implementation of the SHA-1 hash algorithm, which\n>>   outperforms the default fallback implementation we borrowed from\n>>   Mozilla.\n>>\n>>  * Unnecessary inefficiency in deepening of a shallow repository has\n>>   been removed.\n>>\n>>  * \"git clone\" does not grab objects that it does not need (i.e.\n>>   referenced only from refs outside refs/heads and refs/tags\n>>   hierarchy) anymore.\n>>\n>>  * The \"git\" main binary used to link with libcurl, which then dragged\n>>   in a large number of external libraries.  When using basic plumbing\n>>   commands in scripts, this unnecessarily slowed things down.  We now\n>>   implement http/https/ftp transfer as a separate executable as we\n>>   used to.\n>>\n>>  * \"git clone\" run locally hardlinks or copies the files in .git/ to\n>>   newly created repository.  It used to give new mtime to copied files,\n>>   but this delayed garbage collection to trigger unnecessarily in the\n>>   cloned repository.  We now preserve mtime for these files to avoid\n>>   this issue.\n>>\n>> (usability, bells and whistles)\n>>\n>>  * Human writable date format to various options, e.g. --since=yesterday,\n>>   master@{2000.09.17}, are taught to infer some omitted input properly.\n>>\n>>  * A few programs gave verbose \"advice\" messages to help uninitiated\n>>   people when issuing error messages.  An infrastructure to allow\n>>   users to squelch them has been introduced, and a few such messages\n>>   can be silenced now.\n>>\n>>  * refs/replace/ hierarchy is designed to be usable as a replacement\n>>   of the \"grafts\" mechanism, with the added advantage that it can be\n>>   transferred across repositories.\n>>\n>>  * \"git am\" learned to optionally ignore whitespace differences.\n>>\n>>  * \"git am\" handles input e-mail files that has CRLF line endings sensibly.\n>>\n>>  * \"git am\" learned \"--scissors\" option to allow you to discard early part\n>>   of an incoming e-mail.\n>>\n>>  * \"git archive -o output.zip\" works without being told what format to\n>>   use with an explicit \"--format=zip\".option.\n>>\n>>  * \"git checkout\", \"git reset\" and \"git stash\" learned to pick and\n>>   choose to use selected changes you made, similar to \"git add -p\".\n>>\n>>  * \"git clone\" learned a \"-b\" option to pick a HEAD to check out\n>>   different from the remote's default branch.\n>>\n>>  * \"git clone\" learned --recursive option.\n>>\n>>  * \"git clone\" from a local repository on a different filesystem used to\n>>   copy individual object files without preserving the old timestamp, giving\n>>   them extra lifetime in the new repository until they gc'ed.\n>>\n>>  * \"git commit --dry-run $args\" is a new recommended way to ask \"what would\n>>   happen if I try to commit with these arguments.\"\n>>\n>>  * \"git commit --dry-run\" and \"git status\" shows conflicted paths in a\n>>   separate section to make them easier to spot during a merge.\n>>\n>>  * \"git cvsimport\" now supports password-protected pserver access even\n>>   when the password is not taken from ~/.cvspass file.\n>>\n>>  * \"git fast-export\" learned --no-data option that can be useful when\n>>   reordering commits and trees without touching the contents of\n>>   blobs.\n>>\n>>  * \"git fast-import\" has a pair of new front-end in contrib/ area.\n>>\n>>  * \"git init\" learned to mkdir/chdir into a directory when given an\n>>   extra argument (i.e. \"git init this\").\n>>\n>>  * \"git instaweb\" optionally can use mongoose as the web server.\n>>\n>>  * \"git log --decorate\" can optionally be told with --decorate=full to\n>>   give the reference name in full.\n>>\n>>  * \"git merge\" issued an unnecessarily scary message when it detected\n>>   that the merge may have to touch the path that the user has local\n>>   uncommitted changes to. The message has been reworded to make it\n>>   clear that the command aborted, without doing any harm.\n>>\n>>  * \"git push\" can be told to be --quiet.\n>>\n>>  * \"git push\" pays attention to url.$base.pushInsteadOf and uses a URL\n>>   that is derived from the URL used for fetching.\n>>\n>>  * informational output from \"git reset\" that lists the locally modified\n>>   paths is made consistent with that of \"git checkout $another_branch\".\n>>\n>>  * \"git submodule\" learned to give submodule name to scripts run with\n>>   \"foreach\" subcommand.\n>>\n>>  * various subcommands to \"git submodule\" learned --recursive option.\n>>\n>>  * \"git submodule summary\" learned --files option to compare the work\n>>   tree vs the commit bound at submodule path, instead of comparing\n>>   the index.\n>>\n>>  * \"git upload-pack\", which is the server side support for \"git clone\" and\n>>   \"git fetch\", can call a new post-upload-pack hook for statistics purposes.\n>>\n>> (developers)\n>>\n>>  * With GIT_TEST_OPTS=\"--root=/p/a/t/h\", tests can be run outside the\n>>   source directory; using tmpfs may give faster turnaround.\n>>\n>>  * With NO_PERL_MAKEMAKER set, DESTDIR= is now honoured, so you can\n>>   build for one location, and install into another location to tar it\n>>   up.\n>>\n>> Fixes since v1.6.4\n>> ------------------\n>>\n>> All of the fixes in v1.6.4.X maintenance series are included in this\n>> release, unless otherwise noted.\n>> --\n>> To unsubscribe from this list: send the line \"unsubscribe git\" in\n>> the body of a message to majordomo@vger.kernel.org\n>> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>>\n>\n"},{"id":"124626","messageId":"7vfx9pydhk.fsf@alter.siamese.dyndns.org","threadId":"21187","inReplyTo":"f488382f0910110930u1af92299ld5d72dbb31ed1914@mail.gmail.com","subject":"Re: [ANNOUNCE] GIT 1.6.5","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-10-11T18:47:19Z","receivedAt":"2009-10-11T18:47:19Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Steven Noonan writes:\n\n> Uh-oh.\n>\n> Alcarin:crisscross steven$ git remote update\n> Updating origin\n> fatal: 'git@github.com/tycho/crisscross.git' does not appear to be a\n> git repository\n> fatal: The remote end hung up unexpectedly\n> error: Could not fetch origin\n\nTry user@site:path/to/repo.git with a colon. As you mentioned already,\nyou could also use ssh://user@site/full/path/to/repo.git\n\n> The 'ssh://' part is omitted in numerous places on github.com. I\n> realize github.com isn't the final authority on the syntax of the URI,\n\nWhat do you mean by \"final authority\"?\n\nYour misconfigured URL is diagnosed by the local client on your end and I\ndo not think it has anything to do with github. Do you mean github.com\ndocumentation primarily uses scp syntax (i.e. [user@]site:path/to/repo)\ninstead of the fake URI syntax (i.e. ssh://user@site/full/path/to/repo),\n*but* misspells the former without colon (i.e. [user@]site/path/to/repo)?\n\nIf that is the case, it is something github folks need to fix, but I doubt\nthey have such a breakage.\n\n> but was this an intentional change or a regression?\n\nI do not think older clients ever allowed your colon-less scp syntax. Do\nyou really see any *change*? IOW, not the difference between the ssh://\nsyntax and a misspelled scp syntax, but a difference between versions of\ngit working and not working with a misspelled scp syntax?\n\nWhich version of git worked with \"git@github.com/tycho/crisscross.git\" for\nyou?\n"},{"id":"124628","messageId":"f488382f0910111157s6089cf21y254e0c706b35cd33@mail.gmail.com","threadId":"21187","inReplyTo":"7vfx9pydhk.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] GIT 1.6.5","fromName":"Steven Noonan","fromEmail":"steven@uplinklabs.net","sentAt":"2009-10-11T18:57:53Z","receivedAt":"2009-10-11T18:57:53Z","isPatch":false,"sender":{"key":"steven@uplinklabs.net","avatar":"https://gravatar.com/avatar/b0cd397a10638433f76e084531aa0af3bef85f8fdb59b1ebe2ddaf168cd100e9?d=mp&s=160"},"body":"On Sun, Oct 11, 2009 at 11:47 AM, Junio C Hamano wrote:\n> Steven Noonan writes:\n>\n>> Uh-oh.\n>>\n>> Alcarin:crisscross steven$ git remote update\n>> Updating origin\n>> fatal: 'git@github.com/tycho/crisscross.git' does not appear to be a\n>> git repository\n>> fatal: The remote end hung up unexpectedly\n>> error: Could not fetch origin\n>\n> Try user@site:path/to/repo.git with a colon.  As you mentioned already,\n> you could also use ssh://user@site/full/path/to/repo.git\n\nOops. You're right, of course. I'm going on 4 hours of sleep in 2\ndays, so needless to say I'm not at my best right now. Sorry for the\nnoise.\n\n>\n>> The 'ssh://' part is omitted in numerous places on github.com. I\n>> realize github.com isn't the final authority on the syntax of the URI,\n>\n> What do you mean by \"final authority\"?\n\nI didn't want to imply that \"github says to do it this way, so git\nshould follow\".\n"},{"id":"125026","messageId":"m3fx9lfwwr.fsf@localhost.localdomain","threadId":"21187","inReplyTo":"7v8wfi1fya.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] GIT 1.6.5","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2009-10-14T22:11:50Z","receivedAt":"2009-10-14T22:11:50Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Junio C Hamano writes:\n\n> The latest feature release GIT 1.6.5 is available at the usual\n> places:\n> \n> http://www.kernel.org/pub/software/scm/git/\n> \n> git-1.6.5.tar.{gz,bz2}\t\t\t(source tarball)\n> git-htmldocs-1.6.5.tar.{gz,bz2}\t\t(preformatted docs)\n> git-manpages-1.6.5.tar.{gz,bz2}\t\t(preformatted docs)\n> \n> The RPM binary packages for a few architectures are found in:\n> \n> RPMS/$arch/git-*-1.6.5-1.fc9.$arch.rpm\t(RPM)\n> \n> This cycle took a bit longer than I hoped, but here it is. We already\n> have some new features cooking in 'next', and I expect we may be able to\n> have 1.6.6 by the end of the year.\n\nCompiling git from source RPM git-1.6.5-1.fc9.src.rpm using\n\n $ rpmbuild --rebuild git-1.6.5-1.fc9.src.rpm\n\nfails with the following error:\n\n SUBDIR perl\n/usr/bin/perl Makefile.PL PREFIX='/usr'\nOnly one of PREFIX or INSTALL_BASE can be given. Not both.\nmake[1]: *** [perl.mak] Error 2\nmake: *** [perl/perl.mak] Error 2\nerror: Bad exit status from /var/tmp/rpm-tmp.53174 (%build)\n\nCompiling git from source with\n\n $ make prefix=/home/local/git \\\n bindir=/home/local/git \\\n gitexecdir=/home/local/git \\\n template_dir=/home/local/git \\\n GIT_PYTHON_DIR=/home/local/git \n\ngives the same error.\n\nIt might matter that I am using modern Perl way of installing Perl\nmodules locally, via local::lib, with ~/perl5/.modulebuildrc\ncontaining \n\n install --install_base /home/jnareb/perl5\n\nand I have\n\n export MODULEBUILDRC=\"$HOME/perl5/.modulebuildrc\"\n export PERL_MM_OPT=\"INSTALL_BASE=$HOME/perl5\"\n\nDoing\n\n $ unset PERL_MM_OPT\n\nbefore compiling (from SRPMS) made compilation pass this stage,\nand finally succeed.\n\nI guess that perl/Makefile (or rather the file that generates it)\nshould unset PERL_MM_OPT, or use INSTALL_BASE as DESTDIR rather\nthan fiddling with PREFIX.\n\n\nBut I am not a Perl hacker\n------------------------------------------------------------\nperl, v5.8.6\nExtUtils::MakeMaker 6.54 (local)\nExtUtils::MakeMaker 6.17 (global)\n\nexport MODULEBUILDRC=\"$HOME/perl5/.modulebuildrc\"\nexport PERL_MM_OPT=\"INSTALL_BASE=$HOME/perl5\"\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"125285","messageId":"4ADB4AE8.5070007@hartwork.org","threadId":"21187","inReplyTo":"7v8wfi1fya.fsf@alter.siamese.dyndns.org","subject":"Re: [ANNOUNCE] GIT 1.6.5","fromName":"Sebastian Pipping","fromEmail":"webmaster@hartwork.org","sentAt":"2009-10-18T17:05:44Z","receivedAt":"2009-10-18T17:05:44Z","isPatch":false,"sender":{"key":"webmaster@hartwork.org","avatar":null},"body":"Junio C Hamano wrote:\n> * \"git push\" can be told to be --quiet.\n\nIf I'm not mistaken --quiet is not documented in the git-push man page.\nThis includes release 1.6.5.1.\n\n\n\nSebastian\n"},{"id":"125310","messageId":"20091018235240.GU6115@genesis.frugalware.org","threadId":"21187","inReplyTo":"4ADB4AE8.5070007@hartwork.org","subject":"[PATCH] Document git push -q","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2009-10-18T23:52:40Z","receivedAt":"2009-10-18T23:52:40Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"Signed-off-by: Miklos Vajna \n---\n\nOn Sun, Oct 18, 2009 at 07:05:44PM +0200, Sebastian Pipping wrote:\n> If I'm not mistaken --quiet is not documented in the git-push man page.\n> This includes release 1.6.5.1.\n\nHere is a patch to document it.\n\n Documentation/git-push.txt | 6 ++++++\n 1 files changed, 6 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex ba6a8a2..beb3422 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -138,6 +138,12 @@ useful if you write an alias or script around 'git-push'.\n --verbose::\n \tRun verbosely.\n \n+-q::\n+--quiet::\n+\tSome transports produce output even without `--verbose` turned\n+\ton. This provides a way to tell them to be more quiet (whereas\n+\tsimply redirecting might lose error messages).\n+\n include::urls-remotes.txt[]\n \n OUTPUT\n-- \n1.6.5\n"},{"id":"125320","messageId":"20091019115412.6117@nanako3.lavabit.com","threadId":"21187","inReplyTo":"20091018235240.GU6115@genesis.frugalware.org","subject":"[PATCH] git push: remove incomplete options list from help text","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2009-10-19T02:54:12Z","receivedAt":"2009-10-19T02:54:12Z","isPatch":true,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"'git push -h' shows usage text with incomplete list of options and then\nhas a separate list of options that are supported. Imitate the way other\ncommands (I looked at 'git diff' for an example) show their options.\n\nSigned-off-by: しらいし ななこ \n---\nQuoting Miklos Vajna \n\n> Signed-off-by: Miklos Vajna \n> ---\n>\n> On Sun, Oct 18, 2009 at 07:05:44PM +0200, Sebastian Pipping wrote:\n>> If I'm not mistaken --quiet is not documented in the git-push man page.\n>> This includes release 1.6.5.1.\n>\n> Here is a patch to document it.\n\n% git push -h\nusage: git push [--all | --mirror] [-n | --dry-run] [--porcelain] [--tags]\n[--receive-pack=] [--repo=] [-f | --force]\n[-v] [ ...]\n\n -q, --quiet be quiet\n -v, --verbose be verbose\n --repo repository\n --all push all refs\n --mirror mirror all refs\n --tags push tags\n -n, --dry-run dry run\n --porcelain machine-readable output\n -f, --force force updates\n --thin use thin pack\n --receive-pack \n receive pack program\n --exec \n receive pack program\n\n builtin-push.c | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/builtin-push.c b/builtin-push.c\nindex 3cb1ee4..6686b79 100644\n--- a/builtin-push.c\n+++ b/builtin-push.c\n@@ -10,7 +10,7 @@\n #include \"parse-options.h\"\n \n static const char * const push_usage[] = {\n-\t\"git push [--all | --mirror] [-n | --dry-run] [--porcelain] [--tags] [--receive-pack=] [--repo=] [-f | --force] [-v] [ ...]\",\n+\t\"git push [ ...]\",\n \tNULL,\n };\n \n-- \n1.6.5.rc1.18.g53a9a\n\n\n\n\n-- \nNanako Shiraishi\nhttp://ivory.ap.teacup.com/nanako3/\n"},{"id":"125323","messageId":"7vpr8kcc00.fsf@alter.siamese.dyndns.org","threadId":"21187","inReplyTo":"20091019115412.6117@nanako3.lavabit.com","subject":"Re: [PATCH] git push: remove incomplete options list from help text","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-10-19T03:13:03Z","receivedAt":"2009-10-19T03:13:03Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Nanako Shiraishi writes:\n\n> 'git push -h' shows usage text with incomplete list of options and then\n> has a separate list of options that are supported. Imitate the way other\n> commands (I looked at 'git diff' for an example) show their options.\n>\n> Signed-off-by: しらいし ななこ \n> ---\n> ...\n> diff --git a/builtin-push.c b/builtin-push.c\n> index 3cb1ee4..6686b79 100644\n> --- a/builtin-push.c\n> +++ b/builtin-push.c\n> @@ -10,7 +10,7 @@\n> #include \"parse-options.h\"\n> \n> static const char * const push_usage[] = {\n> -\t\"git push [--all | --mirror] [-n | --dry-run] [--porcelain] [--tags] [--receive-pack=] [--repo=] [-f | --force] [-v] [ ...]\",\n> +\t\"git push [ ...]\",\n> \tNULL,\n> };\n> \n> -- \n> 1.6.5.rc1.18.g53a9a\n\nSounds like a sane thing to do, but I am sort of surprised that you are\nstill on 1.6.5-rc1 ;-)\n\nHow does this interact with one of the \"unapplied patch\" you reminded me\nof, namely, this one:\n\n From:\tBjörn Gustavsson \n Subject: [PATCH] push: fix usage: --tags is incompatible with --all and --mirror\n Date:\tThu, 15 Oct 2009 18:39:05 +0200\n Message-ID: <4AD75029.1010109@gmail.com>\n\n Correct the usage text to make it clear that --tags cannot\n be combined with --all or --mirror.\n\nThe option description that comes from parse-options may need to be\nupdated as well, no?\n\n> -q, --quiet be quiet\n> -v, --verbose be verbose\n> --repo repository\n> --all push all refs\n> --mirror mirror all refs\n> --tags push tags\n> -n, --dry-run dry run\n> --porcelain machine-readable output\n> -f, --force force updates\n> --thin use thin pack\n> --receive-pack \n> receive pack program\n> --exec \n> receive pack program\n"},{"id":"125324","messageId":"20091019125701.6117@nanako3.lavabit.com","threadId":"21187","inReplyTo":"7vpr8kcc00.fsf@alter.siamese.dyndns.org","subject":"[PATCH] git push: say that --tag can't be used with --all or --mirror in help text","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2009-10-19T03:57:01Z","receivedAt":"2009-10-19T03:57:01Z","isPatch":true,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"This replaces an earlier patch by Björn Gustavsson,\n\n Message-ID: <4AD75029.1010109@gmail.com>\n\nSigned-off-by: しらいし ななこ \n---\n builtin-push.c | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/builtin-push.c b/builtin-push.c\nindex 6686b79..d7248f2 100644\n--- a/builtin-push.c\n+++ b/builtin-push.c\n@@ -181,7 +181,7 @@ int cmd_push(int argc, const char **argv, const char *prefix)\n \t\tOPT_BIT( 0 , \"all\", &flags, \"push all refs\", TRANSPORT_PUSH_ALL),\n \t\tOPT_BIT( 0 , \"mirror\", &flags, \"mirror all refs\",\n \t\t\t (TRANSPORT_PUSH_MIRROR|TRANSPORT_PUSH_FORCE)),\n-\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags\"),\n+\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags (can't be used with --all nor --mirror\"),\n \t\tOPT_BIT('n' , \"dry-run\", &flags, \"dry run\", TRANSPORT_PUSH_DRY_RUN),\n \t\tOPT_BIT( 0, \"porcelain\", &flags, \"machine-readable output\", TRANSPORT_PUSH_PORCELAIN),\n \t\tOPT_BIT('f', \"force\", &flags, \"force updates\", TRANSPORT_PUSH_FORCE),\n-- \n1.6.5.rc1.18.g53a9a\n\n\n\n\n-- \nNanako Shiraishi\nhttp://ivory.ap.teacup.com/nanako3/\n"},{"id":"125326","messageId":"20091019040119.GA7170@coredump.intra.peff.net","threadId":"21187","inReplyTo":"20091018235240.GU6115@genesis.frugalware.org","subject":"Re: [PATCH] Document git push -q","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-19T04:01:19Z","receivedAt":"2009-10-19T04:01:19Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Oct 19, 2009 at 01:52:40AM +0200, Miklos Vajna wrote:\n\n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index ba6a8a2..beb3422 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -138,6 +138,12 @@ useful if you write an alias or script around 'git-push'.\n> --verbose::\n> \tRun verbosely.\n> \n> +-q::\n> +--quiet::\n> +\tSome transports produce output even without `--verbose` turned\n> +\ton. This provides a way to tell them to be more quiet (whereas\n> +\tsimply redirecting might lose error messages).\n> +\n\nThanks, though two complaints:\n\n 1. This is not just about \"some transports\". Some of the quieted code\n is in transport_push, so hopefully it applies to all transports\n once they follow that code path (though we also pass the quiet flag\n on to pack-objects, so that part is about \"some transports\".\n\n 2. Maybe it would be more helpful to the user to describe what is\n shown and what is not. I think we want to claim to suppress all\n non-error output (since that was the intent of the recent patches).\n If that is not true for some transport, then we need to fix passing\n --quiet to that transport.\n\n...Ah, I see your confusion. You read the log for afdeeb00, but there\nwere some follow-on patches that impacted others part of push. :)\n\nSo maybe this instead:\n\n-- >8 --\nSubject: [PATCH] document push's new quiet option\n\n\nSigned-off-by: Jeff King \n---\n Documentation/git-push.txt | 5 +++++\n 1 files changed, 5 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex ba6a8a2..37c8895 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -138,6 +138,11 @@ useful if you write an alias or script around 'git-push'.\n --verbose::\n \tRun verbosely.\n \n+-q::\n+--quiet::\n+\tSuppress all output, including the listing of updated refs,\n+\tunless an error occurs.\n+\n include::urls-remotes.txt[]\n \n OUTPUT\n-- \n1.6.5.1.121.g65c47\n"},{"id":"125327","messageId":"20091019041033.GB7170@coredump.intra.peff.net","threadId":"21187","inReplyTo":"20091019115412.6117@nanako3.lavabit.com","subject":"Re: [PATCH] git push: remove incomplete options list from help text","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-19T04:10:34Z","receivedAt":"2009-10-19T04:10:34Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Oct 19, 2009 at 11:54:12AM +0900, Nanako Shiraishi wrote:\n\n> static const char * const push_usage[] = {\n> -\t\"git push [--all | --mirror] [-n | --dry-run] [--porcelain] [--tags] [--receive-pack=] [--repo=] [-f | --force] [-v] [ ...]\",\n> +\t\"git push [ ...]\",\n\nThis is a big improvement, IMO. We should probably standardize on when\nto show options, and when to simply say , and make sure every\nprogram does the right thing. I am in favor of a short synopsis followed\nby a list (as you do here) for both usage and for manpages. However, I\nraised the question a few weeks ago and the response was slightly\nnegative:\n\n http://thread.gmane.org/gmane.comp.version-control.git/129399/focus=129424\n\nProbably few people read it, as it was buried deep in a thread. But\nmaybe we should settle on a rule like \"short synopsis for usage, long\nsynopsis for manpage\" or whatever people think is best.\n\nAlso, minor nit with your patch: should it be \"[]\"?\n\n-Peff\n"},{"id":"125328","messageId":"20091019041401.GC7170@coredump.intra.peff.net","threadId":"21187","inReplyTo":"20091019125701.6117@nanako3.lavabit.com","subject":"Re: [PATCH] git push: say that --tag can't be used with --all or --mirror in help text","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-19T04:14:01Z","receivedAt":"2009-10-19T04:14:01Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Oct 19, 2009 at 12:57:01PM +0900, Nanako Shiraishi wrote:\n\n> -\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags\"),\n> +\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags (can't be used with --all nor --mirror\"),\n\nGrammar nit: I believe it should be \"or\" and not \"nor\".\n\nThere is an implicit \"either\", as in \"can't be used with either --all or\n--mirror\". Saying \"can't be used with neither --all nor --mirror\" would\nbe a double-negative. The alternative correct single-negation would be\n\"can be used with neither --all nor --mirror\".\n\n-Peff\n"},{"id":"125333","messageId":"7v3a5gaqkt.fsf@alter.siamese.dyndns.org","threadId":"21187","inReplyTo":"20091019041033.GB7170@coredump.intra.peff.net","subject":"Re: [PATCH] git push: remove incomplete options list from help text","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-10-19T05:41:06Z","receivedAt":"2009-10-19T05:41:06Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> Probably few people read it, as it was buried deep in a thread. But\n> maybe we should settle on a rule like \"short synopsis for usage, long\n> synopsis for manpage\" or whatever people think is best.\n>\n> Also, minor nit with your patch: should it be \"[]\"?\n\nThanks, I agree with you on both counts.\n"},{"id":"125336","messageId":"7vtyxv7wmi.fsf@alter.siamese.dyndns.org","threadId":"21187","inReplyTo":"20091018235240.GU6115@genesis.frugalware.org","subject":"Re: [PATCH] Document git push -q","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-10-19T05:58:45Z","receivedAt":"2009-10-19T05:58:45Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thanks; applied.\n"},{"id":"125604","messageId":"20091021144203.GA30485@coredump.intra.peff.net","threadId":"21187","inReplyTo":"20091019125701.6117@nanako3.lavabit.com","subject":"Re: [PATCH] git push: say that --tag can't be used with --all or --mirror in help text","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-10-21T14:42:03Z","receivedAt":"2009-10-21T14:42:03Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Oct 19, 2009 at 12:57:01PM +0900, Nanako Shiraishi wrote:\n\n> -\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags\"),\n> +\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags (can't be used with --all nor --mirror\"),\n\nHmm. We apparently all managed to miss this typo. It's visually hard to\nnotice because of the \")\" closing the macro.\n\n-- >8 --\nSubject: [PATCH] push: fix typo in usage\n\nMissing \")\".\n\nSigned-off-by: Jeff King \n---\n builtin-push.c | 2 +-\n 1 files changed, 1 insertions(+), 1 deletions(-)\n\ndiff --git a/builtin-push.c b/builtin-push.c\nindex 7d78711..019c986 100644\n--- a/builtin-push.c\n+++ b/builtin-push.c\n@@ -181,7 +181,7 @@ int cmd_push(int argc, const char **argv, const char *prefix)\n \t\tOPT_BIT( 0 , \"all\", &flags, \"push all refs\", TRANSPORT_PUSH_ALL),\n \t\tOPT_BIT( 0 , \"mirror\", &flags, \"mirror all refs\",\n \t\t\t (TRANSPORT_PUSH_MIRROR|TRANSPORT_PUSH_FORCE)),\n-\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags (can't be used with --all or --mirror\"),\n+\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags (can't be used with --all or --mirror)\"),\n \t\tOPT_BIT( 0 , \"purge\", &flags,\n \t\t\t\"remove locally deleted refs from remote\",\n \t\t\tTRANSPORT_PUSH_PURGE),\n-- \n1.6.5.1.139.g6f544.dirty\n"},{"id":"125645","messageId":"20091022062135.6117@nanako3.lavabit.com","threadId":"21187","inReplyTo":"20091021144203.GA30485@coredump.intra.peff.net","subject":"Re: [PATCH] git push: say that --tag can't be used with --all or --mirror in help text","fromName":"Nanako Shiraishi","fromEmail":"nanako3@lavabit.com","sentAt":"2009-10-21T21:21:35Z","receivedAt":"2009-10-21T21:21:35Z","isPatch":true,"sender":{"key":"nanako3@lavabit.com","avatar":"https://gravatar.com/avatar/3777b9e201c5883a62b1a6fdf7c53f2d712d1d80989146063ea861e33aad72a8?d=mp&s=160"},"body":"Quoting Jeff King \n\n> On Mon, Oct 19, 2009 at 12:57:01PM +0900, Nanako Shiraishi wrote:\n>\n>> -\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags\"),\n>> +\t\tOPT_BOOLEAN( 0 , \"tags\", &tags, \"push tags (can't be used with --all nor --mirror\"),\n>\n> Hmm. We apparently all managed to miss this typo. It's visually hard to\n> notice because of the \")\" closing the macro.\n\nHow embarrassing. Thank you for a fix.\n\n-- \nNanako Shiraishi\nhttp://ivory.ap.teacup.com/nanako3/\n"}]}