{"thread":{"id":"34374","subject":"[PATCH 0/2] Avoid suggestions to \"merge\" remote changes","startedAt":"2013-07-07T19:02:13Z","lastAt":"2013-07-08T18:47:16Z","messageCount":5,"participants":["John Keeping","Matthieu Moy"],"isPatch":true,"patchVersion":1,"patchTotal":2},"messages":[{"id":"222769","messageId":"cover.1373223663.git.john@keeping.me.uk","threadId":"34374","inReplyTo":null,"subject":"[PATCH 0/2] Avoid suggestions to \"merge\" remote changes","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-07-07T19:02:13Z","receivedAt":"2013-07-07T19:02:13Z","isPatch":true,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"As another aspect of the change to make git-pull die when remote changes\ndo not fast-forward, this series changes the advice messages in git-push to\navoid implying that the user wants to merge remote changes.\n\nI've chosen the word \"integrate\" because it does not carry any special\nmeaning in Git (in terms of being a command) and seems to cover the\nmerge and rebase cases nicely.\n\nJohn Keeping (2):\n  push: avoid suggesting \"merging\" remote changes\n  pull: change the description to \"integrate\" changes\n\n Documentation/git-pull.txt |  2 +-\n builtin/push.c             | 12 ++++++------\n git-pull.sh                |  2 +-\n 3 files changed, 8 insertions(+), 8 deletions(-)\n\n-- \n1.8.3.2.855.gbc9faed\n"},{"id":"222770","messageId":"2a6f4a3c31e667aa03b06ce63ae5319a25beaca0.1373223663.git.john@keeping.me.uk","threadId":"34374","inReplyTo":"cover.1373223663.git.john@keeping.me.uk","subject":"[PATCH 1/2] push: avoid suggesting \"merging\" remote changes","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-07-07T19:02:14Z","receivedAt":"2013-07-07T19:02:14Z","isPatch":true,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"With some workflows, it is more suitable to rebase on top of remote\nchanges when a push does not fast-forward.  Change the advice messages\nin git-push to suggest that a user \"integrate the remote changes\"\ninstead of \"merge the remote changes\" to make this slightly clearer.\n\nAlso change the suggested 'git pull' to 'git pull ...' to hint to users\nthat they may want to add other parameters.\n\nSuggested-by: Philip Oakley <philipoakley@iee.org>\nSigned-off-by: John Keeping <john@keeping.me.uk>\n---\n builtin/push.c | 12 ++++++------\n 1 file changed, 6 insertions(+), 6 deletions(-)\n\ndiff --git a/builtin/push.c b/builtin/push.c\nindex 2d84d10..44e53cd 100644\n--- a/builtin/push.c\n+++ b/builtin/push.c\n@@ -211,8 +211,8 @@ static void setup_default_push_refspecs(struct remote *remote)\n \n static const char message_advice_pull_before_push[] =\n \tN_(\"Updates were rejected because the tip of your current branch is behind\\n\"\n-\t   \"its remote counterpart. Merge the remote changes (e.g. 'git pull')\\n\"\n-\t   \"before pushing again.\\n\"\n+\t   \"its remote counterpart. Integrate the remote changes (e.g.\\n\"\n+\t   \"'git pull ...') before pushing again.\\n\"\n \t   \"See the 'Note about fast-forwards' in 'git push --help' for details.\");\n \n static const char message_advice_use_upstream[] =\n@@ -223,15 +223,15 @@ static const char message_advice_use_upstream[] =\n \n static const char message_advice_checkout_pull_push[] =\n \tN_(\"Updates were rejected because a pushed branch tip is behind its remote\\n\"\n-\t   \"counterpart. Check out this branch and merge the remote changes\\n\"\n-\t   \"(e.g. 'git pull') before pushing again.\\n\"\n+\t   \"counterpart. Check out this branch and integrate the remote changes\\n\"\n+\t   \"(e.g. 'git pull ...') before pushing again.\\n\"\n \t   \"See the 'Note about fast-forwards' in 'git push --help' for details.\");\n \n static const char message_advice_ref_fetch_first[] =\n \tN_(\"Updates were rejected because the remote contains work that you do\\n\"\n \t   \"not have locally. This is usually caused by another repository pushing\\n\"\n-\t   \"to the same ref. You may want to first merge the remote changes (e.g.,\\n\"\n-\t   \"'git pull') before pushing again.\\n\"\n+\t   \"to the same ref. You may want to first integrate the remote changes\\n\"\n+\t   \"(e.g., 'git pull ...') before pushing again.\\n\"\n \t   \"See the 'Note about fast-forwards' in 'git push --help' for details.\");\n \n static const char message_advice_ref_already_exists[] =\n-- \n1.8.3.2.855.gbc9faed\n"},{"id":"222771","messageId":"c13c6c4b15d1cfcaa140a8d71676ce330c32e9b9.1373223663.git.john@keeping.me.uk","threadId":"34374","inReplyTo":"cover.1373223663.git.john@keeping.me.uk","subject":"[PATCH 2/2] pull: change the description to \"integrate\" changes","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-07-07T19:02:15Z","receivedAt":"2013-07-07T19:02:15Z","isPatch":true,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"Since git-pull learned the --rebase option it has not just been about\nmerging changes from a remote repository (where \"merge\" is in the sense\nof \"git merge\").  Change the description to use \"integrate\" instead of\n\"merge\" in order to reflect this.\n\nSigned-off-by: John Keeping <john@keeping.me.uk>\n---\n Documentation/git-pull.txt | 2 +-\n git-pull.sh                | 2 +-\n 2 files changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt\nindex 24ab07a..6ef8d59 100644\n--- a/Documentation/git-pull.txt\n+++ b/Documentation/git-pull.txt\n@@ -3,7 +3,7 @@ git-pull(1)\n \n NAME\n ----\n-git-pull - Fetch from and merge with another repository or a local branch\n+git-pull - Fetch from and integrate with another repository or a local branch\n \n \n SYNOPSIS\ndiff --git a/git-pull.sh b/git-pull.sh\nindex 6828e2c..ecf0011 100755\n--- a/git-pull.sh\n+++ b/git-pull.sh\n@@ -5,7 +5,7 @@\n # Fetch one or more remote refs and merge it/them into the current HEAD.\n \n USAGE='[-n | --no-stat] [--[no-]commit] [--[no-]squash] [--[no-]ff] [-s strategy]... [<fetch-options>] <repo> <head>...'\n-LONG_USAGE='Fetch one or more remote refs and merge it/them into the current HEAD.'\n+LONG_USAGE='Fetch one or more remote refs and integrate it/them into the current HEAD.'\n SUBDIRECTORY_OK=Yes\n OPTIONS_SPEC=\n . git-sh-setup\n-- \n1.8.3.2.855.gbc9faed\n"},{"id":"222825","messageId":"vpqd2qtkvtk.fsf@anie.imag.fr","threadId":"34374","inReplyTo":"2a6f4a3c31e667aa03b06ce63ae5319a25beaca0.1373223663.git.john@keeping.me.uk","subject":"Re: [PATCH 1/2] push: avoid suggesting \"merging\" remote changes","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2013-07-08T13:47:19Z","receivedAt":"2013-07-08T13:47:19Z","isPatch":true,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"John Keeping <john@keeping.me.uk> writes:\n\n>  static const char message_advice_pull_before_push[] =\n>  \tN_(\"Updates were rejected because the tip of your current branch is behind\\n\"\n> -\t   \"its remote counterpart. Merge the remote changes (e.g. 'git pull')\\n\"\n> -\t   \"before pushing again.\\n\"\n> +\t   \"its remote counterpart. Integrate the remote changes (e.g.\\n\"\n> +\t   \"'git pull ...') before pushing again.\\n\"\n\nTo me, \"merge\" includes \"rebase\", so I'd say the merge -> integrate\nchange is not needed, but I have nothing against it either.\n\nThe \"...\" added are a bit weird with the quotes around. Quotes may\nsuggest that the content is to be taken literally, which is not the case\nanymore. Not a real objection anyway, just thinking aloud.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"222854","messageId":"20130708184715.GW9161@serenity.lan","threadId":"34374","inReplyTo":"vpqd2qtkvtk.fsf@anie.imag.fr","subject":"Re: [PATCH 1/2] push: avoid suggesting \"merging\" remote changes","fromName":"John Keeping","fromEmail":"john@keeping.me.uk","sentAt":"2013-07-08T18:47:16Z","receivedAt":"2013-07-08T18:47:16Z","isPatch":true,"sender":{"key":"john@keeping.me.uk","avatar":"https://avatars.githubusercontent.com/u/1702081?v=4"},"body":"On Mon, Jul 08, 2013 at 03:47:19PM +0200, Matthieu Moy wrote:\n> John Keeping <john@keeping.me.uk> writes:\n> \n> >  static const char message_advice_pull_before_push[] =\n> >  \tN_(\"Updates were rejected because the tip of your current branch is behind\\n\"\n> > -\t   \"its remote counterpart. Merge the remote changes (e.g. 'git pull')\\n\"\n> > -\t   \"before pushing again.\\n\"\n> > +\t   \"its remote counterpart. Integrate the remote changes (e.g.\\n\"\n> > +\t   \"'git pull ...') before pushing again.\\n\"\n> \n> To me, \"merge\" includes \"rebase\", so I'd say the merge -> integrate\n> change is not needed, but I have nothing against it either.\n\nYes, I agree that in some sense \"merge\" does include \"rebase\" but I\nsuspect some people read it to mean \"git merge\" and saying \"integrate\"\nremoves that potential source of confusion.\n\n> The \"...\" added are a bit weird with the quotes around. Quotes may\n> suggest that the content is to be taken literally, which is not the case\n> anymore. Not a real objection anyway, just thinking aloud.\n\nI hadn't thought of it that way, but I wonder how else we can delimit\nthe command.\n"}]}