Junio C Hamano wrote:
>> The pseudo ref certainly has an appeal. For people very familiar with
>> Git's peculiarities such as FETCH_HEAD. Such as myself.
>> For users, it is probably substantially worse an experience than having a
>> cmdmode like --show-patch in the very
Johannes Schindelin writes:
> The pseudo ref certainly has an appeal. For people very familiar with
> Git's peculiarities such as FETCH_HEAD. Such as myself.
>
> For users, it is probably substantially worse an experience than having a
> cmdmode like --show-patch in
Hi Duy,
On Tue, 30 Jan 2018, Duy Nguyen wrote:
> On Mon, Jan 29, 2018 at 10:09 PM, Johannes Schindelin
> wrote:
> > Hi Duy,
> >
> > On Fri, 26 Jan 2018, Nguyễn Thái Ngọc Duy wrote:
> >
> >> When a conflict happens during a rebase, you often need to look at the
> >>
On Mon, Jan 29, 2018 at 10:09 PM, Johannes Schindelin
wrote:
> Hi Duy,
>
> On Fri, 26 Jan 2018, Nguyễn Thái Ngọc Duy wrote:
>
>> When a conflict happens during a rebase, you often need to look at the
>> original patch to see what the changes are. This requires opening
Hi Duy,
On Fri, 26 Jan 2018, Nguyễn Thái Ngọc Duy wrote:
> When a conflict happens during a rebase, you often need to look at the
> original patch to see what the changes are. This requires opening your
> favourite pager with some random path inside $GIT_DIR.
>
> This series makes that
On Fri, Jan 26 2018, Nguyễn Thái Ngọc Duy jotted:
> When a conflict happens during a rebase, you often need to look at the
> original patch to see what the changes are. This requires opening your
> favourite pager with some random path inside $GIT_DIR.
>
> This series makes that experience a bit
On Sat, Jan 27, 2018 at 1:47 AM, Tim Landscheidt
wrote:
> Nguyễn Thái Ngọc Duy wrote:
>
>> When a conflict happens during a rebase, you often need to look at the
>> original patch to see what the changes are. This requires opening your
>> favourite
Nguyễn Thái Ngọc Duy wrote:
> When a conflict happens during a rebase, you often need to look at the
> original patch to see what the changes are. This requires opening your
> favourite pager with some random path inside $GIT_DIR.
> This series makes that experience a bit
When a conflict happens during a rebase, you often need to look at the
original patch to see what the changes are. This requires opening your
favourite pager with some random path inside $GIT_DIR.
This series makes that experience a bit better, by providing a command
to read the patch. This is
9 matches
Mail list logo