mirror of
https://github.com/facebook/sapling.git
synced 2024-10-10 16:57:49 +03:00
87e672961e
This avoids conflict with the core extension (`hgext/sparse.py`). In development mode, the `hgext` version takes precedence and people can easily use the wrong sparse extension. `sparse.py` is kept for compatibility. Differential Revision: https://phab.mercurial-scm.org/D1048
42 lines
924 B
Perl
42 lines
924 B
Perl
Make sure the sparse extension does not break functionality when it gets
|
|
loaded in a non-sparse repository.
|
|
|
|
First create a base repository with sparse enabled.
|
|
|
|
$ hg init base
|
|
$ cd base
|
|
$ cat > .hg/hgrc <<EOF
|
|
> [extensions]
|
|
> sparse=$TESTDIR/../hgext3rd/fbsparse.py
|
|
> journal=
|
|
> EOF
|
|
|
|
$ echo a > file1
|
|
$ echo x > file2
|
|
$ hg ci -Aqm 'initial'
|
|
$ cd ..
|
|
|
|
Now create a shared working copy that is not sparse.
|
|
|
|
$ hg --config extensions.share= share base shared
|
|
updating working directory
|
|
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
$ cd shared
|
|
$ cat > .hg/hgrc <<EOF
|
|
> [extensions]
|
|
> share=
|
|
> sparse=!
|
|
> journal=
|
|
> EOF
|
|
|
|
Make sure "hg diff" works in the non-sparse working directory.
|
|
|
|
$ echo z >> file1
|
|
$ hg diff
|
|
diff -r 1f02e070b36e file1
|
|
--- a/file1 Thu Jan 01 00:00:00 1970 +0000
|
|
+++ b/file1 Thu Jan 01 00:00:00 1970 +0000
|
|
@@ -1,1 +1,2 @@
|
|
a
|
|
+z
|