so -m 0 is it? I'm confused.

On 2/18/2012 3:13 PM, Alex wrote:
> Yeah, it seems like it reverts all of the merged-in commits in one
> huge go. (arguably beneficial considering the amount of commits...)
>
> Regards,
> Alex
>
> On Sun, Feb 19, 2012 at 12:10 AM, Martin Nowak<dawg@dawgfoto.de>  wrote:
>>> git revert -m 0 would have worked.
>>> The number indexes the parent branch.
>>>
>> OK indexing starts at 1 and it works for me too. It only creates one commit
>> though.
>>
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On Sun, 19 Feb 2012 01:14:18 +0100, Walter Bright <walter@digitalmars.com> wrote:

> so -m 0 is it? I'm confused.
>
Sorry for the noise. It's -m 1. It will create ONE commit that reverts all changes relative to parent 1.
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On 2/19/2012 9:19 AM, Martin Nowak wrote:
> On Sun, 19 Feb 2012 01:14:18 +0100, Walter Bright <walter@digitalmars.com> wrote:
>
>> so -m 0 is it? I'm confused.
>>
> Sorry for the noise. It's -m 1. It will create ONE commit that reverts all changes relative to parent 1.
>

Thanks!
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals