1 |
On 12/10/2011 03:45 PM, William Hubbs wrote: |
2 |
>> - supports branching catalyst_2 off master, too |
3 |
|
4 |
s/catalyst_2/catalyst_3/ |
5 |
|
6 |
|
7 |
> The method you are suggesting does _NOT_ make the current content of |
8 |
> master appear on catalyst_3, which is the other part of what releng is |
9 |
> requesting. |
10 |
|
11 |
That's a trivial addition. With it, the full run on my shell: |
12 |
|
13 |
# git branch catalyst_3 master |
14 |
|
15 |
# git checkout master |
16 |
|
17 |
# git merge $(git commit-tree catalyst_2^{tree} \ |
18 |
-p catalyst_2 -p master \ |
19 |
<<<"Replace content on master with content from catalyst_2") |
20 |
|
21 |
# git push origin master |
22 |
|
23 |
# git push origin catalyst_3 |
24 |
|
25 |
|
26 |
Results is: |
27 |
|
28 |
- 2.x content on branch master (and catalyest_2) |
29 |
|
30 |
- 3.x content on branch catalyest_3 |
31 |
|
32 |
|
33 |
> What I think I can do, but I'm not quite sure how to do it, is: |
34 |
> |
35 |
> 1) create a catalyst_3 branch at the same point in history where |
36 |
> catalyst_2 was created. I believe I can accomplish this with |
37 |
> |
38 |
> git branch catalyst_3 $(git merge-base master catalyst_2) |
39 |
|
40 |
The branch head is moving along with each commit so it would end up at |
41 |
the current master in the end, anyway. |
42 |
|
43 |
If you like to mark the point where catalyst 3.x was started, a tag |
44 |
would be the right tool, not a branch. |
45 |
|
46 |
|
47 |
> 2) put the code on master that is _NOT_ on catalyst_2 on catalyst_3. |
48 |
> |
49 |
> Any suggestions for how to do this? |
50 |
|
51 |
I'm not sure what you mean by that. |
52 |
|
53 |
|
54 |
> 3) put the code on catalyst_2 on master. |
55 |
> |
56 |
> What about this? |
57 |
|
58 |
Either git commit-tree or forced push. |
59 |
|
60 |
Best, |
61 |
|
62 |
|
63 |
|
64 |
Sebastian |