Re: [PATCH v2 0/3] Accommodate for pu having been renamed to seen

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Junio,

On Wed, 24 Jun 2020, Junio C Hamano wrote:

> Junio C Hamano <gitster@xxxxxxxxx> writes:
>
> > "Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx>
> > writes:
> >
> >> Changes since v1:
> >>
> >>  * Rebased onto master (no conflicts, so it is safe, and it is more robust
> >>    than basing the patches on seen which already contains v1 of these
> >>    patches).
> >
> > Thanks, I actually wanted to include it in 'maint', so I'll queue on
> > the same base (no conflicts, so it is safe, and it will be in a
> > maintenance release if we are going to issue one).
>
> By the way, I find myself typing 'pu' all the time, even though I've
> been using 'seen' for almost 48 hours by now.  My private tooling
> all have been updated to work with 'seen', but it seems that it
> takes time to retrain muscle memory.  I'll see if I can fully adjust
> before the next week starts.

I do understand the issue. If you're as addicted to tab-completion as I
am, something like `pulse` might have made that transition.

Ciao,
Dscho

> I do not know how many of you regularly have interacted with 'pu'
> and now need to go through the same adjustment as I do.  Sorry for
> using you as a guinea pig for an experiment for you know what to
> gauge the cost.





[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux