{"thread":{"id":"6401","subject":"[PATCH] document --exec for git-push","startedAt":"2007-01-16T15:02:02Z","lastAt":"2007-01-16T19:45:20Z","messageCount":2,"participants":["Uwe Kleine-König","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"31823","messageId":"20070116150201.GA2427@cepheus","threadId":"6401","inReplyTo":null,"subject":"[PATCH] document --exec for git-push","fromName":"Uwe Kleine-König","fromEmail":"zeisberg@informatik.uni-freiburg.de","sentAt":"2007-01-16T15:02:02Z","receivedAt":"2007-01-16T15:02:02Z","isPatch":true,"sender":{"key":"u.kleine-koenig@pengutronix.de","avatar":"https://gravatar.com/avatar/354b5e3ceb2806a2f1e1e382ac29ddbdad18288654da62b61eb13583a857eee7?d=mp&s=160"},"body":"The text is just copied from git-send-pack.txt.\n\nSigned-off-by: Uwe Kleine-König <zeisberg@informatik.uni-freiburg.de>\n---\n Documentation/git-push.txt |    8 +++++++-\n 1 files changed, 7 insertions(+), 1 deletions(-)\n\nThere are still some options undocumented, but I don't know what they\ndo exacly:\n\n\t--thin\n\t--no-thin\n\t--repo=\n\t-v\n\n(OK, I just now saw -v and I'm to lazy to do it now :-)\n\nBest regards\nUwe\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 197f4b5..a19631d 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -8,7 +8,7 @@ git-push - Update remote refs along with associated objects\n \n SYNOPSIS\n --------\n-'git-push' [--all] [--tags] [-f | --force] <repository> <refspec>...\n+'git-push' [--all] [--tags] [--exec=<receive-pack>] [-f | --force] <repository> <refspec>...\n \n DESCRIPTION\n -----------\n@@ -67,6 +67,12 @@ the remote repository.\n \taddition to refspecs explicitly listed on the command\n \tline.\n \n+\\--exec::\n+\tPath to the 'git-receive-pack' program on the remote\n+\tend.  Sometimes useful when pushing to a remote\n+\trepository over ssh, and you do not have the program in\n+\ta directory on the default $PATH.\n+\n -f, \\--force::\n \tUsually, the command refuses to update a remote ref that is\n \tnot a descendant of the local ref used to overwrite it.\n-- \n1.5.0.rc1.g581a\n\n-- \nUwe Kleine-König\n\nhttp://www.google.com/search?q=72+PS+point+in+inch\n"},{"id":"31838","messageId":"7vk5zmycvj.fsf@assigned-by-dhcp.cox.net","threadId":"6401","inReplyTo":"20070116150201.GA2427@cepheus","subject":"Re: [PATCH] document --exec for git-push","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2007-01-16T19:45:20Z","receivedAt":"2007-01-16T19:45:20Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Uwe Kleine-König  <zeisberg@informatik.uni-freiburg.de> writes:\n\n> The text is just copied from git-send-pack.txt.\n\nThanks.\n\n> There are still some options undocumented, but I don't know what they\n> do exacly:\n>\n> \t--thin\n> \t--no-thin\n> \t--repo=\n> \t-v\n\nUsually a good way to answer that question is:\n\n\t$ git blame -C -L'/^int cmd_push/,/^}/' builtin-push.c\n\nand then run \"git show\" on the commit that introduces the option\nparsing, e.g. commit bcc785f6 for --repo.\n\n----------------------------------------------------------------\ncommit bcc785f611dc6084be75999a3b6bafcc950e21d6\nAuthor: Linus Torvalds <torvalds@osdl.org>\nDate:   Mon Oct 30 08:28:59 2006 -0800\n\ngit push: add verbose flag and allow overriding of default target repository\n\nThis adds a command line flag \"-v\" to enable a more verbose mode, and\n\"--repo=\" to override the default target repository for \"git push\" (which\notherwise always defaults to \"origin\").\n\nThis, together with the patch to allow dashes in config variable names,\nallows me to do\n\n\t[alias]\n\t\tpush-all = push -v --repo=all\n\nin my user-global config file, and then I can (for any project I maintain)\nadd to the project-local config file\n\n\t[remote \"all\"]\n\t\turl=one.target.repo:/directory\n\t\turl=another.target:/pub/somewhere/else\n\nand now \"git push-all\" just updates all the target repositories, and shows\nme what it does - regardless of which repo I am in.\n\n----------------------------------------------------------------\n\nBut now I wonder why Linus couldn't have just done:\n\n\t[alias]\n\t\tpush-all = push -v all\n\n-- >8 --\ngit-push documentation: remaining bits\n\nMention --thin, --no-thin, --repo and -v. \n\n---\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex a19631d..3e8dbcf 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -8,7 +8,7 @@ git-push - Update remote refs along with associated objects\n \n SYNOPSIS\n --------\n-'git-push' [--all] [--tags] [--exec=<receive-pack>] [-f | --force] <repository> <refspec>...\n+'git-push' [--all] [--tags] [--exec=<receive-pack>]  [--repo=all] [-f | --force] [--thin | --no-thin] [-v] [<repository> <refspec>...]\n \n DESCRIPTION\n -----------\n@@ -79,6 +79,18 @@ the remote repository.\n \tThis flag disables the check.  This can cause the\n \tremote repository to lose commits; use it with care.\n \n+\\--repo=<repo>::\n+\tWhen no repository is specified the command defaults to\n+\t\"origin\"; this overrides it.\n+\n+\\--thin, \\--no-thin::\n+\tThese options are passed to `git-send-pack`.  Thin\n+\ttransfer spends extra cycles to minimize the number of\n+\tobjects to be sent and meant to be used on slower connection.\n+\n+-v::\n+\tRun verbosely.\n+\n include::urls.txt[]\n \n Author\n"}]}