Mercurial > hg > mercurial
view mercurial-tests/testData/bin/help/diffs.txt @ 1132:a272ea98b4b7 development/2024.07.x tip
TW-88158: remove MercurialCommitsInfoBuilderSupport and CommitsAndMountPointsCommand together with the custom hg extension.
- The extension point was introduced for Upsource and is no longer needed.
- The hg extension was not compatible with python 3 and led to test errors.
(grafted from cb5e6f9a2bcd450e660c89305b190f5ed272e0d6)
author | Andreas Eisele <andreas.eisele@jetbrains.com> |
---|---|
date | Thu, 06 Jun 2024 15:12:18 +0200 |
parents | 2e52f00a3c94 |
children |
line wrap: on
line source
Mercurial's default format for showing changes between two versions of a file is compatible with the unified format of GNU diff, which can be used by GNU patch and many other standard tools. While this standard format is often enough, it does not encode the following information: - executable status and other permission bits - copy or rename information - changes in binary files - creation or deletion of empty files Mercurial also supports the extended diff format from the git VCS which addresses these limitations. The git diff format is not produced by default because a few widespread tools still do not understand this format. This means that when generating diffs from a Mercurial repository (e.g. with "hg export"), you should be careful about things like file copies and renames or other things mentioned above, because when applying a standard diff to a different repository, this extra information is lost. Mercurial's internal operations (like push and pull) are not affected by this, because they use an internal binary format for communicating changes. To make Mercurial produce the git extended diff format, use the --git option available for many commands, or set 'git = True' in the [diff] section of your hgrc. You do not need to set this option when importing diffs in this format or using them in the mq extension.