[Pharo-dev] Support understanding changes

Camillo Bruni camillobruni at gmail.com
Wed Nov 6 08:33:37 EST 2013


>> Indeed, some meta data is needed, although I think much of it can be properly inferred if the commits have sufficient resolution. As a side note, git for instance does not track renames:
>> 	https://git.wiki.kernel.org/index.php/Git_FAQ#Why_does_Git_not_.22track.22_renames.3F
>> 	http://permalink.gmane.org/gmane.comp.version-control.git/217
>> Specially the last link is worth reading ;)
> 
> Yes, this seems probable, but we need to try to be sure.

definitely, for now this sounds more like an optimization, sticking to the full metadata seems to be easier.


>> If you attach the information to the commit itself that will be fine: 	
>> 	https://www.kernel.org/pub/software/scm/git/docs/git-notes.html
>> 
>> because, as you say, each time metadata ends up in the sources part of the git
>> repository we will have merge problems, since you can only properly merge such
>> data if you fully understand the semantic meaning.
> 
> Hum. Reading git notes say that there is a merge operation involved...

haha, yeah thought the same ;), though I never used notes, so I have to try that out first..

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 447 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131106/c84497b2/attachment.asc>


More information about the Pharo-dev mailing list