{"thread":{"id":"21982","subject":"How to commit bug fixes from old revisions","startedAt":"2009-12-18T15:02:05Z","lastAt":"2009-12-18T15:15:46Z","messageCount":2,"participants":["Richard Rossel","Howard Miller"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"130072","messageId":"4B2B996D.9070302@inf.utfsm.cl","threadId":"21982","inReplyTo":null,"subject":"How to commit bug fixes from old revisions","fromName":"Richard Rossel","fromEmail":"rrossel@inf.utfsm.cl","sentAt":"2009-12-18T15:02:05Z","receivedAt":"2009-12-18T15:02:05Z","isPatch":false,"sender":{"key":"rrossel@inf.utfsm.cl","avatar":null},"body":"Hi,\nI'm confused with how to commit bug fixes from old tagged version.\nLets says that I have a serie of tags (v1.0, v1.1, v1.2, v2.0) in master,\nand there is a bug from v.1.2. The bug was fixed, but I don't\nwant to merge to v2.0, because there are not compatibles. The bug fixed \nshould be\ntagged as v1.3\n\nSo the question is how to commit between revisions( in the example, \nbetween v.1.2 and v2.0),\nwithout made any change in the HEAD of master (v2.0)\n\nOr maybe the solution is to separate the versions  in different branches \nor different repos.\n\nThanks for the help\n\n-- \nRichard Rossel\nSoftware Engineer at Airsage Inc.\nValparaiso - Chile\n"},{"id":"130074","messageId":"26ae428a0912180715v15d85fbcm9fef7c33f6ccf448@mail.gmail.com","threadId":"21982","inReplyTo":"4B2B996D.9070302@inf.utfsm.cl","subject":"Re: How to commit bug fixes from old revisions","fromName":"Howard Miller","fromEmail":"howardsmiller@googlemail.com","sentAt":"2009-12-18T15:15:46Z","receivedAt":"2009-12-18T15:15:46Z","isPatch":false,"sender":{"key":"howardsmiller@googlemail.com","avatar":"https://gravatar.com/avatar/69a7274bc5c4c66910b00e4ea6590e46e2325b53ff4807854f3ed469b49400b1?d=mp&s=160"},"body":"2009/12/18 Richard Rossel <rrossel@inf.utfsm.cl>:\n> Hi,\n> I'm confused with how to commit bug fixes from old tagged version.\n> Lets says that I have a serie of tags (v1.0, v1.1, v1.2, v2.0) in master,\n> and there is a bug from v.1.2. The bug was fixed, but I don't\n> want to merge to v2.0, because there are not compatibles. The bug fixed\n> should be\n> tagged as v1.3\n>\n> So the question is how to commit between revisions( in the example, between\n> v.1.2 and v2.0),\n> without made any change in the HEAD of master (v2.0)\n>\n> Or maybe the solution is to separate the versions  in different branches or\n> different repos.\n\nI think it depends on how you look at it.  The tag implies that v1.3\nis a fixed release but what you say implies a branch. What I would do\nis have a (say) '1.3_RELEASE\" branch and that has the various fixes\nmerged on it. To put it another way, does your fix mean that there'll\nbe a v1.3.1? If so you would be tagging that on the 1.3 branch\n(probably).\n\nHTH\n"}]}