Re: If merging that is really fast forwarding creates new commit
- From
- Rocco Rutte <pdmef@gmx.net>
- Date
- Nov 6, 2006, 13:39 UTC
- Message-ID
- <20061106133923.GB1151@robert.daprodeges.fqdn.th-h.de>
- In-Reply-To
- <454F31D7.1030202@gmail.com>
Hi,
* Liu Yubao [06-11-06 21:00:07 +0800] wrote:
>Then, what bad *logical* problem will happen if a merging that is really a fast forwarding creates a new commit?
I don't know what you expect by "logical" nor if I get you right, but if fast-forward merge a branch to another one, both branches now have exactly the same hash. If you create a commit object for a fast-forward merge, both tip hashes not identical anymore... which is bad.
The identical hash important so that you really know they're identical and for future reference like ancestry.
bye, Rocco