{"thread":{"id":"2407","subject":"[PATCH] Update howto using-topic-branches","startedAt":"2005-11-08T23:52:02Z","lastAt":"2005-11-08T23:52:02Z","messageCount":1,"participants":["Luck, Tony"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"11359","messageId":"200511082352.jA8Nq2fW007877@agluck-lia64.sc.intel.com","threadId":"2407","inReplyTo":null,"subject":"[PATCH] Update howto using-topic-branches","fromName":"Luck, Tony","fromEmail":"tony.luck@intel.com","sentAt":"2005-11-08T23:52:02Z","receivedAt":"2005-11-08T23:52:02Z","isPatch":true,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":"\"git resolve\" is being deprecated in favour of \"git merge\".\nUpdate the documentation to reflect this.\n\nSigned-off-by: Tony Luck <tony.luck@intel.com>\n\n---\n\nUntested ... I'll update my real scripts to do it this way soon.\n\ndiff --git a/Documentation/howto/using-topic-branches.txt b/Documentation/howto/using-topic-branches.txt\nindex c6c635a..4698abe 100644\n--- a/Documentation/howto/using-topic-branches.txt\n+++ b/Documentation/howto/using-topic-branches.txt\n@@ -9,7 +9,7 @@ GIT as a Linux subsystem maintainer.\n \n -Tony\n \n-Last updated w.r.t. GIT 0.99.5\n+Last updated w.r.t. GIT 0.99.9f\n \n Linux subsystem maintenance using GIT\n -------------------------------------\n@@ -89,8 +89,8 @@ out at the current tip of the linus bran\n \n These can be easily kept up to date by merging from the \"linus\" branch:\n \n- $ git checkout test && git resolve test linus \"Auto-update from upstream\"\n- $ git checkout release && git resolve release linus \"Auto-update from upstream\"\n+ $ git checkout test && git merge \"Auto-update from upstream\" test linus\n+ $ git checkout release && git merge \"Auto-update from upstream\" release linus\n \n Set up so that you can push upstream to your public tree (you need to\n log-in to the remote system and create an empty tree there before the\n@@ -128,7 +128,7 @@ commit to this branch.\n When you are happy with the state of this change, you can pull it into the\n \"test\" branch in preparation to make it public:\n \n- $ git checkout test && git resolve test speed-up-spinlocks \"Pull speed-up-spinlock changes\"\n+ $ git checkout test && git merge \"Pull speed-up-spinlock changes\" test speed-up-spinlocks\n \n It is unlikely that you would have any conflicts here ... but you might if you\n spent a while on this step and had also pulled new versions from upstream.\n@@ -138,7 +138,7 @@ same branch into the \"release\" tree read\n see the value of keeping each patch (or patch series) in its own branch.  It\n means that the patches can be moved into the \"release\" tree in any order.\n \n- $ git checkout release && git resolve release speed-up-spinlocks \"Pull speed-up-spinlock changes\"\n+ $ git checkout release && git merge \"Pull speed-up-spinlock changes\" release speed-up-spinlocks\n \n After a while, you will have a number of branches, and despite the\n well chosen names you picked for each of them, you may forget what\n@@ -190,7 +190,7 @@ Here are some of the scripts that I use \n \n case \"$1\" in\n test|release)\n-\tgit checkout $1 && git resolve $1 linus \"Auto-update from upstream\"\n+\tgit checkout $1 && git merge \"Auto-update from upstream\" $1 linus\n \t;;\n linus)\n \tbefore=$(cat .git/refs/heads/linus)\n@@ -231,7 +231,7 @@ test|release)\n \t\techo $1 already merged into $2 1>&2\n \t\texit 1\n \tfi\n-\tgit checkout $2 && git resolve $2 $1 \"Pull $1 into $2 branch\"\n+\tgit checkout $2 && git merge \"Pull $1 into $2 branch\" $2 $1\n \t;;\n *)\n \tusage\n"}]}