SZEDER Gábor sze...@ira.uka.de writes:
Now, __git_complete_revlist_file() provides completion both for this
master:DocTAB notation and for revision ranges, i.e. for
master..nTAB and master...nTAB. However, since neither git
ls-tree nor git archive accept revision ranges, calling
SZEDER Gábor wrote:
Well, people out there might have completion scriplets for their
aliases or custom git commands which use __git_complete_file().
Removing this function would break those scripts.
What is the advantage of using __git_complete_file() over
__git_complete_revlist_file()? Isn't
On Fri, Jun 07, 2013 at 10:51:53PM +0530, Ramkumar Ramachandra wrote:
SZEDER Gábor wrote:
Well, people out there might have completion scriplets for their
aliases or custom git commands which use __git_complete_file().
Removing this function would break those scripts.
What is the
Ramkumar Ramachandra artag...@gmail.com writes:
Junio C Hamano wrote:
I think this is the same as 5/6 and better explained in a single
patch, as the rationale is the same: these commands can all take the
usual revs and then paths, so using misnamed complete_FILE helper is
wrong.
Mind if I
Ramkumar Ramachandra artag...@gmail.com writes:
Currently, the 'git ls-tree', 'git archive', and 'git show' completions
use __git_complete_file (aliased to __git_complete_revlist_file).
In the case of 'git ls-tree' and 'git archive', they necessarily require
a tree-ish argument (and
Ramkumar Ramachandra artag...@gmail.com writes:
Currently, the 'git ls-tree', 'git archive', and 'git show' completions
use __git_complete_file (aliased to __git_complete_revlist_file).
In the case of 'git ls-tree' and 'git archive', they necessarily require
a tree-ish argument (and
On Sun, Jun 02, 2013 at 07:33:42PM +0530, Ramkumar Ramachandra wrote:
Currently, the 'git ls-tree', 'git archive', and 'git show' completions
use __git_complete_file (aliased to __git_complete_revlist_file).
In the case of 'git ls-tree' and 'git archive', they necessarily require
a tree-ish
7 matches
Mail list logo
