mirror of
https://github.com/facebook/sapling.git
synced 2024-10-08 15:57:43 +03:00
1e4894d773
The default behaviour is to commit subrepositories with uncommitted changes. In my experience this is usually undesirable: - Changes to dependencies are often debugging leftovers - Real changes should generally be applied on the source project directly, tested then committed. This is not always possible, subversion subrepos may include only a small part of the source project, without the tests. Setting ui.commitsubrepos=no will now abort commits containing such modified subrepositories like: $ hg --config ui.commitsubrepos=no ci -m msg abort: uncommitted changes in subrepo sub I ruled out the hook solution because it does not easily take --include/exclude options in account. Also, my main concern is whether this flag could cause problems with extensions. If there are legitimate reasons for callers to override this behaviour (I could not find any), they might either override at ui level, or we could add an argument to localrepo.commit() later. v2: - Renamed ui.commitsubs to ui.commitsubrepos - Mention the configuration entry in hg help subrepos |
||
|---|---|---|
| .. | ||
| config.txt | ||
| dates.txt | ||
| diffs.txt | ||
| environment.txt | ||
| extensions.txt | ||
| glossary.txt | ||
| hgweb.txt | ||
| merge-tools.txt | ||
| multirevs.txt | ||
| patterns.txt | ||
| revisions.txt | ||
| revsets.txt | ||
| subrepos.txt | ||
| templates.txt | ||
| urls.txt | ||