Re: [RFC PATCH 0/4] Add alias option to git branch

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

Re: [RFC PATCH 4/4] Add alias option to git branch

5/03/19 5:23 AM, Kenneth Cochran wrote: > Adding Phil for comments Thank you for following this up, Kenneth. I'll do some testing with your patch sometime soon. I've realised that the last version of my script that I posted to the mailing list was buggy, and that in wanting to hold off sending a

Re: Feature request: Provide porcelain to manage symbolic references as branch aliases

Updating the proof-of-concept script for this feature request. (See attachment.) I'm quoting the entire original message for reference, just because it's been a while since I proposed this. -Phil On 30/04/14 00:51, Phil Sainty wrote: > Most of the plumbing for having branch

Since 2.7.0 git branch displays symbolic references as ref -> ref instead of ref -> branch

Given the following symbolic reference: $ git symbolic-ref refs/heads/m refs/heads/master Correct in 2.6.6: $ PATH=~/git/git-2.6.6:$PATH git branch m -> master * master Wrong in 2.7.0: $ PATH=~/git/git-2.7.0:$PATH git branch m -> m * master Still wrong in current version 2.8.0: $ PAT

Feature request: Provide porcelain to manage symbolic references as branch aliases

Most of the plumbing for having branch name aliases already exists in the form of symbolic references, and people do use them for this purpose; but I get the impression that it's not really supported officially, and I'm not aware of any porcelain features to facilitate this use-case. I'd like to p