Sun, 13 Dec 2015 19:57:54 +0900 export: remove useless comparison between file object and string
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Dec 2015 19:57:54 +0900] rev 27417
export: remove useless comparison between file object and string It was introduced at 31aa2e5b0750, where "template" argument could be a file object. After that, a306837f8c87 added "len(template)", so "template" must be a string now. Therefore, "fp != template" should always be True. It seems 31aa2e5b0750 was intended to work around a bug in TortoiseHg, and I'm sure I've fixed it completely in TortoiseHg source. https://selenic.com/pipermail/mercurial-devel/2011-February/028467.html
Sun, 13 Dec 2015 19:47:46 +0900 export: do not print '<fdopen>' as an output filename
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Dec 2015 19:47:46 +0900] rev 27416
export: do not print '<fdopen>' as an output filename Because makefileobj() duplicates or wraps stdout, "fp != sys.stdout" didn't work correctly. Python doc states that special file objects are named in the form '<...>', and absolute filenames should never start with '<', we can ignore names start with '<'. We can't test fp.fileno() because fp may be a command-server channel. https://docs.python.org/2.7/library/stdtypes.html#file.name In the test output, "exporting patch:" line is printed after patch content. This is caused by fdopen() and will be fixed by the subsequent patch.
Sun, 13 Dec 2015 19:32:01 +0900 commandserver: implement name() to clarify channel is not a plain file
Yuya Nishihara <yuya@tcha.org> [Sun, 13 Dec 2015 19:32:01 +0900] rev 27415
commandserver: implement name() to clarify channel is not a plain file Because unknown attributes are delegated to the underlying file object, commandserver channels said they were '<stdout>' or '<stdin>' even though they weren't. This patch makes them say '<X-channel>'.
Tue, 15 Dec 2015 13:27:09 -0800 histedit: delete to drop
Mateusz Kwapich <mitrandir@fb.com> [Tue, 15 Dec 2015 13:27:09 -0800] rev 27414
histedit: delete to drop The default behaviour to forbid this makes a lot of sense for novice users because it's safeguarding them from dangerous behavior but making it configurable will be apprieciated by power users in at least one big organization. It allows an user to look an histedit rules from declarative perspective and make the rules reflect the state after histedit. If we can move lines t move commits why can't we drop lines to drop commits? Let's put this behind config knob and inform users about this feature the very moment they are trying to use it so they can choose desired behaviour.
Wed, 16 Dec 2015 12:33:54 +0100 clonebundles: fix bundlespec typo
Mathias De Maré <mathias.demare@gmail.com> [Wed, 16 Dec 2015 12:33:54 +0100] rev 27413
clonebundles: fix bundlespec typo
Thu, 17 Dec 2015 20:13:29 +0000 record: fix hunk handling to remember the current function
timeless <timeless@mozdev.org> [Thu, 17 Dec 2015 20:13:29 +0000] rev 27412
record: fix hunk handling to remember the current function
Thu, 17 Dec 2015 14:38:22 +0000 record: turn on showfunc
timeless <timeless@mozdev.org> [Thu, 17 Dec 2015 14:38:22 +0000] rev 27411
record: turn on showfunc Always try to give diff context when doing an interactive record
Thu, 17 Dec 2015 13:07:34 -0800 parsers: use PyTuple_Pack instead of manual list-filling
Bryan O'Sullivan <bos@serpentine.com> [Thu, 17 Dec 2015 13:07:34 -0800] rev 27410
parsers: use PyTuple_Pack instead of manual list-filling Suggested by Yuya.
Thu, 17 Dec 2015 15:23:36 -0800 tags: mention --quiet switch in help (issue4920)
Thu Trang Pham <thu@fb.com> [Thu, 17 Dec 2015 15:23:36 -0800] rev 27409
tags: mention --quiet switch in help (issue4920)
Thu, 17 Dec 2015 17:27:32 -0600 merge with stable
Matt Mackall <mpm@selenic.com> [Thu, 17 Dec 2015 17:27:32 -0600] rev 27408
merge with stable
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 tip