Recently we introduce the share-safe functionality which makes shares share
requirements and config of share source. This patch adds support to
debugupgraderepo command to upgrade repository to share-safe mode when
format.exp-share-safe config is enabled.
Details
- Reviewers
 marmoute mharbison72 - Group Reviewers
 hg-reviewers - Commits
 - rHG705c37f22859: upgrade: add support for experimental safe share mode
 
Diff Detail
- Repository
 - rHG Mercurial
 - Branch
 - default
 - Lint
 No Linters Available - Unit
 No Unit Test Coverage 
Event Timeline
| mercurial/upgrade.py | ||
|---|---|---|
| 355–357 | 
 Can we upgrade share ? I though it wasn't possible ? And it is probably safer to deny any upgrade from a share. 
 Maybe clarify this using. It makes shares inherit repository requirement and configuration from its source. What do you think ?  | |
| 1463–1465 | Could have have old share automatically pick up the source requirements and move to share safe mode ? That would seems safer.  | |
| tests/test-share-safe.t | ||
| 298–299 | We need to test that downgrading is working too.  | |
| mercurial/upgrade.py | ||
|---|---|---|
| 355–357 | Oh, this message is wrong. Updating it in next version.  | |
| 1463–1465 | They will be required to re-shared. Also I am not sure if we have a way to list all the shares of the current repository.  | |
| tests/test-share-safe.t | ||
| 298–299 | Will add a patch after this one for that functionality.  | |
| mercurial/upgrade.py | ||
|---|---|---|
| 1463–1465 | We don't so we will not be perfect here.  | |
Can we upgrade share ? I though it wasn't possible ? And it is probably safer to deny any upgrade from a share.
Maybe clarify this using. It makes shares inherit repository requirement and configuration from its source.
What do you think ?