| 1 |
Dan Armak wrote: |
| 2 |
> On Saturday 29 April 2006 15:21, Fernando J. Pereda wrote: |
| 3 |
>> The commit marked with @ is a special comit called a 'merge'. |
| 4 |
>> I hope that clarifies the merge tracking part. |
| 5 |
> You just described what merging is. Svn can do that too with svn merge. But, |
| 6 |
> if I merge changesets from branch A to B selectively, skipping some along the |
| 7 |
> way, can I later ask git to: |
| 8 |
> |
| 9 |
> - list the changesets remaining in A that I haven't merged to B yet? |
| 10 |
> - list the branches, from a given list, which have/haven't merged a given |
| 11 |
> changeset? |
| 12 |
> |
| 13 |
> Those are things svn can't do. |
| 14 |
> |
| 15 |
>> However I don't know what do you mean with 'changeset tracking'. |
| 16 |
> |
| 17 |
> I didn't mean that 'changeset tracking' is different from 'merge tracking'. |
| 18 |
|
| 19 |
Subversion dev Daniel Berlin was recently hired by Google, and according to his |
| 20 |
blog[i] one of his first duties is to implement merge tracking in svn. |
| 21 |
|
| 22 |
--de. |
| 23 |
|
| 24 |
|
| 25 |
[i] http://www.dberlin.org/blog/ |
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives