Re: [PATCH] sha1_name.c: add an option to abort on ambiguous refs

Bringing this up again after I've seen another person accidentally create a refs/heads/origin/some-branch and get really confused because "git push" reports up-to-date but the remote branch is not updated. I don't know how he got into that situation, but I hope we should be able to catch it and

Re: [PATCH] sha1_name.c: add an option to abort on ambiguous refs

On Wed, Mar 23, 2016 at 10:45 PM, Johannes Schindelin wrote: > Hi Duy, > > On Wed, 23 Mar 2016, Nguyễn Thái Ngọc Duy wrote: > >> There are cases when a warning on ambiguous refs may go unnoticed >> (e.g. git-log filling up the whole screen). There are also cases when

Re: [PATCH] sha1_name.c: add an option to abort on ambiguous refs

Hi Duy, On Wed, 23 Mar 2016, Nguyễn Thái Ngọc Duy wrote: > There are cases when a warning on ambiguous refs may go unnoticed > (e.g. git-log filling up the whole screen). There are also cases when > people want to catch ambiguity early (e.g. it happens deep in some > script). In either case,

[PATCH] sha1_name.c: add an option to abort on ambiguous refs

There are cases when a warning on ambiguous refs may go unnoticed (e.g. git-log filling up the whole screen). There are also cases when people want to catch ambiguity early (e.g. it happens deep in some script). In either case, aborting the program would accomplish it. Signed-off-by: Nguyễn Thái