comparison hgext3rd/topic/stack.py @ 3225:28fb347a5bf8

typos: fix typos in several locations A user at Google attempted to fix our local copy because they had noticed a typo (accross instead of across), but this will just get overwritten on our next import. This commit fixes that case and a few others that my editor found. Most of the typos were in comments, but user-visible output is changed in a few cases: - accross -> across - splitted -> split - ambigious -> ambiguous - evolvestte -> evolvestate (this is in a ui.debug, so not often seen) There is another typo that I wanted to fix, but didn't: 'supercede' is spelled 'superseed' in a few locations. I believe this is only internal to the extension, instead of being user-visible, so while it could probably be fixed easily, I wasn't 100% sure it didn't end up in a file on disk or something and might cause problems, so I left it alone.
author Kyle Lippincott <spectral@google.com>
date Mon, 04 Dec 2017 14:27:27 -0800
parents 237b39bf7e6b
children e4c0332ecee4
comparison
equal deleted inserted replaced
3224:bac69ab0782c 3225:28fb347a5bf8
260 label='topic.stack.summary.headcount.multiple') 260 label='topic.stack.summary.headcount.multiple')
261 fm.plain(')') 261 fm.plain(')')
262 else: 262 else:
263 if data['behindcount'] == -1: 263 if data['behindcount'] == -1:
264 fm.plain(', ') 264 fm.plain(', ')
265 fm.plain('ambigious rebase destination - %s' % data['behinderror'], 265 fm.plain('ambiguous rebase destination - %s' % data['behinderror'],
266 label='topic.stack.summary.behinderror') 266 label='topic.stack.summary.behinderror')
267 elif data['behindcount']: 267 elif data['behindcount']:
268 fm.plain(', ') 268 fm.plain(', ')
269 fm.plain('%d behind' % data['behindcount'], label='topic.stack.summary.behindcount') 269 fm.plain('%d behind' % data['behindcount'], label='topic.stack.summary.behindcount')
270 fm.plain('\n') 270 fm.plain('\n')