- User Since
- Feb 8 2018, 2:14 AM (19 w, 2 d)
Thu, Jun 21
I need some help with the tests failing here.
Tue, Jun 19
Sun, Jun 17
@yuja Sorry I didn't run the tests after this edit .
Sat, Jun 16
Fri, Jun 15
Wed, Jun 13
I am updating the tests
Tue, Jun 12
Mon, Jun 11
@yuja I am adding an --unmodified flag to change to change the mode to grep on the unmodified files as well.
What I am trying to do is ::
def fns_generator(): if --unmodified: for f in ctx: for f in ctx: if match(f): yield f else : for f in ctx.files(): for f in ctx: if match(f): yield f
Tue, Jun 5
Can you explain why you did this ?
Sat, Jun 2
Wed, May 30
Sat, May 26
Perhaps, we'll have to catch WdirUnsupported error to fall back to the filectx API.
Thu, May 24
So I was working on it, but the way I tried to correct "wdir()" is by handling it as a special case, so introducing an "if" block again similar to this.
But you were asking to eliminate the if/else block altogether, I wonder if there is way ?
Apr 17 2018
fix grep -r 'wdir()'
Apr 3 2018
Mar 27 2018
@yuja Yeah, doing it right away, my bad. I should have based it on some revision which is already in the stable.
Mar 26 2018
Since it required some explanation I have written a post on it.
Mar 25 2018
@yuja Can you please clarify this a bit more?
Mar 24 2018
Mar 23 2018
Mar 10 2018
Mar 9 2018
Since the current code just overwrites message each time with the newer. What can be done to avoid losing the earlier message values?
@durin42 Should I make any changes?
Mar 7 2018
@pulkit Yeah, this rather a not so elegant hack. How can it be parsed in hg commit?
As the first message passed is overwritten by the second one at this step only. :/
@durin42 Even I thought of this construct before as it appears more elegant. But it is failing some tests!
Specifically, the error messages are changed in this one.
Mar 4 2018
@jeffpc That means two new lines. Shall I edit this patch to effect that?
Mar 3 2018
added the tests @krbullock
Mar 2 2018
Feb 23 2018
Oh, I forgot adding tests as @durin42 told. Doing that right away!
What I did: @durin42 suggested in the issue page that the error was in the verify function of the histedit.py file. But when I ran through debugger using a revision number, the code was throwing the error before it reaches the verify function. Specifically in the fromrules function of the histedit.py file.
It was earlier only accepting rulehashes, I changed that to accept any revset using the scmutil.revsingle function suggested by @timeless on the IRC channel.
Feb 18 2018
Oh! Thanks for letting me know!
I will keep that in mind.
Feb 13 2018
Feb 9 2018
@dlax Yes, but the short summary didn't say what it does! It just says "include the specified changeset".