monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-devel] Updated Issue 212 - sync needs list of include patterns


From: code
Subject: [Monotone-devel] Updated Issue 212 - sync needs list of include patterns (monotone)
Date: Sat, 25 Aug 2012 11:49:44 +0200

Hello,

The following issue has been updated:

212 - sync needs list of include patterns
Project: monotone
Status: New
Reported by: Stephen Leake
URL: https://code.monotone.ca/p/monotone/issues/212/
Labels:
 Type:Feature Request
 Priority:Medium

Comments (last first):

# By Stephen Leake, Aug 25, 2012:



 Labels: Type:Feature Request -Type:f 

# 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



--
Issue: https://code.monotone.ca/p/monotone/issues/212/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]