--nextPart5618464.Hjajj26jiS
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

On Monday 10 February 2014 16:40:34, Jes=FAs Gabriel y Gal=E1n=20
<jgabrielygalan / gmail.com> wrote:
> Git tracks the contents of the files, so it's able to follow a rename=

> perfectly fine.

If you (the OP) are interested in the actual background and sementics, =
you can=20
read a question on Stack Exchange regarding this at=20
<http://stackoverflow.com/questions/1094269/whats-the-purpose-of-git-mv=
>,=20
which explains that "git mv" exists and is actual a shortcut for "mv $o=
ld=20
$new; git rm $old; git add $new".

There's a git faq entry at=20
<https://git.wiki.kernel.org/index.php/GitFaq#Why_does_Git_not_.22track=
.22_renames.3F>,=20
and a lengthy explanation by Linus at=20
<http://permalink.gmane.org/gmane.comp.version-control.git/217>.

The short answer is exactly what Jesus said: Git tracks contents, not f=
iles.

HTH.

=09=09=09--- Eric
--nextPart5618464.Hjajj26jiS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAABAgAGBQJS+PciAAoJEIXD2TZ1epVB6zYQAI5I6kzH0PZjuZEBNFrxmBgU
JZKjkpK5tuKPHvMATlx9k3MJoixs4YtRyzVktTRMk22tUO5b0Y5BRd1rtoBIJdb6
J0RPFQ5kunhIt43/ihoWYy2yzEjtGRRJeTO+EYa5I5Pux49TtGo20QNrqU448TzJ
aK2yBc/utm72eq4sYFKY3W/7UjWhHckeIy0uT2PVJDYYhOw+NG7DQZ5wATBtGhAm
LqEdWJdkASyBRftdE7CKPklCzULOsSlUXZ+brwAcsE2TBfR00sQrTOdb2KgtWLit
q0y7nhgE4QGQH5mi09jEH8c6R7gJZMe1zNFWONlqSTH+cCuwNotFuloQPNKobx/X
oH8juJyp0jHLek8rUlPqOXoFHa9xR3FJdiyjRMwXmkHcfRBORvRqRw2Sb8YFdb12
Tbdc3dtO/ydDBcY7zINNAUb1vCz9WRJG4+aZrkMCJsJB7MelQJfZlRWDy0mwsp0G
kJIPX3BClF3l6hX4OIBU14MA7C/woDAp5IgFNqZXzUEDdp7P6x2jvXW+pzGP+vR1
geGQDsNUAj8Mu47u48cPCeQi2dLrhUh3v0YVs2lHHuooHEx4JsPtu6M7TLf7WztJ
Bx3G+dSksBhkVyG4bKc9VwwB/KIk7KvdIN5S4god+86IpFpXIaCH7hZvPScwNqPR
Neo2UY/URtcwY2sCVGi4
=n9Ma
-----END PGP SIGNATURE-----

--nextPart5618464.Hjajj26jiS--