I can only concur about the genuine usefulness of symbolic refs as
branch aliases. I wrote my shell script for this 5 years ago, and
I've made use of the facility almost every working day since.
I jump around branches frequently, and my feature branch names always
start with an issue/bug number f
On Tue, Mar 5, 2019 at 7:21 AM Junio C Hamano wrote:
>
> Kenneth Cochran writes:
>
> > From c1bad54b29ae1c1d8548d248f6ecaa5959e55f7b Mon Sep 17 00:00:00 2001
> > From: Kenneth Cochran
> > Date: Mon, 4 Mar 2019 09:40:22 -0600
> > Subject: [RFC PATCH 0/4] Add
Kenneth Cochran writes:
> From c1bad54b29ae1c1d8548d248f6ecaa5959e55f7b Mon Sep 17 00:00:00 2001
> From: Kenneth Cochran
> Date: Mon, 4 Mar 2019 09:40:22 -0600
> Subject: [RFC PATCH 0/4] Add alias option to git branch
> Cc: Sahil Dua ,
> Duy Nguyen ,
> Jeff King
From c1bad54b29ae1c1d8548d248f6ecaa5959e55f7b Mon Sep 17 00:00:00 2001
From: Kenneth Cochran
Date: Mon, 4 Mar 2019 09:40:22 -0600
Subject: [RFC PATCH 0/4] Add alias option to git branch
Cc: Sahil Dua ,
Duy Nguyen ,
Jeff King
I find myself often using git symbolic-ref to get around work
4 matches
Mail list logo