monotone

Issue 212: sync needs list of include patterns

Reported by Stephen Leake, Aug 25, 2012

We have a database with several branches: 
common.main
common.main_lynx_5
common.mms_version_01

dscovr.dscovr_version_01
dscovr.main
dscovr.main_lynx_5
dscovr.work_dscovr_release
common.work_dscovr_release

gpm.gpm_version_15
gpm.main
gpm.main_lynx_5
common.work_gpm_release
gpm.work_gpm_release

dvc.main
emacs_stephe.main
gds_notes

'common' is shared by all customers; 'dscovr' and 'gpm' are two 
customers. 'dvc.main', 'emacs_stephe.main', gds_notes are tools, 
used by all customers.

'work_*' branches are used for preparing releases.

in the 'dscovr' customer lab, we only want to sync a subset of the 
branches:

common.main
common.main_lynx_5
common.mms_version_01
dscovr.dscovr_version_01
dscovr.main
dscovr.main_lynx_5

dvc.main
emacs_stephe.main
gds_notes

can do this with exclude, but it's tedious, and needs continuous 
maintenance as more customers are added. It would be simpler if the 
sync include pattern was a list.

Output of `mtn version --full`:
-------------------------------

mtn 1.0

Comment 1 by Stephen Leake, Aug 25, 2012

Labels: Type:Feature Request Type:f

Comment 2 by Stephen Leake, Aug 25, 2012

The pre-1.0 sync syntax allowed multiple include patterns (multiple 
GLOBs) and multiple exclude patterns (--exclude options). The 1.0 
URI syntax only allows one include pattern.

Comment 3 by Stephen Leake, Aug 26, 2012

The 1.0 URI syntax does support multiple include patterns; the user 
manual description is wrong. Lua test 
netsync_uri_multi_include_exclude added to demonstrate, manual 
updated in 54bbe85d3580d04a212337c11f075a2b96dabefb
Status: Fixed

Created: 10 years 30 days ago by Stephen Leake

Updated: 10 years 29 days ago

Status: Fixed

Labels:
Type:Feature Request
Priority:Medium

Quick Links:     www.monotone.ca    -     Downloads    -     Documentation    -     Wiki    -     Code Forge    -     Build Status