On 15/04/18 18:17, Philip Oakley wrote:
> From: "Phillip Wood"
> : Friday, April 13, 2018 11:03 AM
>> If a label or reset command fails it is likely to be due to a
>> typo. Rescheduling the command would make it easier for the user to fix
>> the problem as they can just
From: "Phillip Wood"
: Friday, April 13, 2018 11:03 AM
If a label or reset command fails it is likely to be due to a
typo. Rescheduling the command would make it easier for the user to fix
the problem as they can just run 'git rebase --edit-todo'.
Is this worth
On 10/04/18 13:29, Johannes Schindelin wrote:
> In the upcoming commits, we will teach the sequencer to rebase merges.
> This will be done in a very different way from the unfortunate design of
> `git rebase --preserve-merges` (which does not allow for reordering
> commits, or changing the branch
Hi Johannes,
Johannes Schindelin writes:
> Hi Sergey,
>
> On Wed, 11 Apr 2018, Sergey Organov wrote:
>
>> Johannes Schindelin writes:
>>
>> [...]
>>
>> > We disallow '#' as label because that character will be used as
>> > separator in
Hi Sergey,
On Wed, 11 Apr 2018, Sergey Organov wrote:
> Johannes Schindelin writes:
>
> [...]
>
> > We disallow '#' as label because that character will be used as
> > separator in the upcoming `merge` command.
>
> Please consider to use # not only in `merge` and
Hi Johannes,
Johannes Schindelin writes:
[...]
> We disallow '#' as label because that character will be used as separator
> in the upcoming `merge` command.
Please consider to use # not only in `merge` and `reset`, but in the rest
of the commands as well, to unify
In the upcoming commits, we will teach the sequencer to rebase merges.
This will be done in a very different way from the unfortunate design of
`git rebase --preserve-merges` (which does not allow for reordering
commits, or changing the branch topology).
The main idea is to introduce new todo
7 matches
Mail list logo