Re: Using git to track my PhD thesis, couple of questions
- From
- Matthias Andree <matthias.andree@gmx.de>
- Date
- Aug 28, 2009, 13:54 UTC
- Message-ID
- <4A97E1B1.7090107@gmx.de>
- In-Reply-To
- <vpqpragt5bo.fsf@bauges.imag.fr>
Matthieu Moy schrieb:
Show 12 quoted lines
> seanh <seanh.nospam@gmail.com> writes: > >> In response to Matthieu and Paolo, I'm not sure I understand the git >> internals involved in the discussion around merge --squash, I had a >> feeling this would produce a 'merge' that git in some sense would 'not >> know about', > > Yes, that's it. Git does a merge, and immediately forgets it was a > merge. The consequence is when you merge again later, Git will not be > able to use the merge information to be clever about merging. Somehow, > Git will be as bad as SVN for merging if you don't know what you're > doing ;-).
To be fair, SVN versions 1.5 and newer can track merges. If the repository predates 1.5, it has to be updated on the server side (see the release notes for details). It just tracks which revisions have been merged and which not, for further details, see the svn book. (http://svnbook.red-bean.com/ IIRC)