comparison mercurial/obsolete.py @ 32354:f432897a9f49

obsmarker: add an experimental flag controlling "operation" recording It seems better to introduce the experiment behind a flag for now as there are multiple concerns around the feature: * Storing operation increase the size of obsolescence markers significantly (+10-20%). * It performs poorly when exchanging markers (cannot combine command names, command name might be unknown remotely, etc)
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Sat, 20 May 2017 03:10:23 +0200
parents 566cfe9cbbb9
children df448de7cf3b
comparison
equal deleted inserted replaced
32353:4bffe2421f34 32354:f432897a9f49
1244 # prepare metadata 1244 # prepare metadata
1245 if metadata is None: 1245 if metadata is None:
1246 metadata = {} 1246 metadata = {}
1247 if 'user' not in metadata: 1247 if 'user' not in metadata:
1248 metadata['user'] = repo.ui.username() 1248 metadata['user'] = repo.ui.username()
1249 if operation: 1249 useoperation = repo.ui.configbool('experimental',
1250 'evolution.track-operation',
1251 False)
1252 if useoperation and operation:
1250 metadata['operation'] = operation 1253 metadata['operation'] = operation
1251 tr = repo.transaction('add-obsolescence-marker') 1254 tr = repo.transaction('add-obsolescence-marker')
1252 try: 1255 try:
1253 markerargs = [] 1256 markerargs = []
1254 for rel in relations: 1257 for rel in relations: