On 8/9/20 7:38 PM, Uwe Brauer wrote:
Hi
I very use backout rarely. (Either I strip or solve the problem in a
different way).
I realised that I don't really understand its logic.
Take the following script
hg init
echo "First" > test.org
hg add test.org
hg commit -m "0: First"
echo "Second"
>>> "MM" == Malcolm Matalka writes:
> Did you figure hit sout? I just did a test locally and the backout
> worked as expected. In the latest head I ran hg backout -r 2
> --no-commit (I wanted to verify it). When I ran that, I was presented
> with a merge screen to handle the
Did you figure hit sout? I just did a test locally and the backout
worked as expected. In the latest head I ran hg backout -r 2
--no-commit (I wanted to verify it). When I ran that, I was presented
with a merge screen to handle the conflict caused by the backout, and
afterwards I had the
>>> "UB" == Uwe Brauer writes:
> Hi
> I very use backout rarely. (Either I strip or solve the problem in a
> different way).
> I realised that I don't really understand its logic.
> Take the following script
> hg init
> echo "First" > test.org
> hg add test.org
>
Hi
I very use backout rarely. (Either I strip or solve the problem in a
different way).
I realised that I don't really understand its logic.
Take the following script
hg init
echo "First" > test.org
hg add test.org
hg commit -m "0: First"
echo "Second" >> test.org
hg commit -m "1: Second"