On Tue, Sep 25, 2012 at 04:43:59PM -0700, Junio C Hamano wrote:
> SZEDER Gábor writes:
>
> > - test -d "$d/remotes" && ls -1 "$d/remotes"
> > + test -d "$d/remotes" && command ls -1 "$d/remotes"
>
> Yuck. For normal scripts, nobody sane would define "alias" for
> non-interactive environment
On Wed, Sep 26, 2012 at 03:09:38AM +0200, SZEDER Gábor wrote:
> On Wed, Sep 26, 2012 at 01:00:45AM +0200, SZEDER Gábor wrote:
> > But then it got me thinking... Notice how much effort we spend just
> > to get the list of remotes? We could just run 'git remote' directly
> > instead...
>
> Actuall
On Wed, Sep 26, 2012 at 01:00:45AM +0200, SZEDER Gábor wrote:
> But then it got me thinking... Notice how much effort we spend just
> to get the list of remotes? We could just run 'git remote' directly
> instead...
Actually, we can't, because 'git remote' doesn't seem to list remotes
stored unde
SZEDER Gábor writes:
> - test -d "$d/remotes" && ls -1 "$d/remotes"
> + test -d "$d/remotes" && command ls -1 "$d/remotes"
Yuck. For normal scripts, nobody sane would define "alias" for
non-interactive environments, but because these things work in an
interactive environment, we have to
Hi,
On Wed, Sep 19, 2012 at 09:55:28PM +0200, Johannes Sixt wrote:
> I have an empty .git/remotes directory. Trying to complete the name of
> a remote always reports an error:
>
> git@master:1023> git fetch ls: invalid option -- ' '
> Try `ls --help' for more information.
>
> I have these:
>
>
I have an empty .git/remotes directory. Trying to complete the name of
a remote always reports an error:
git@master:1023> git fetch ls: invalid option -- ' '
Try `ls --help' for more information.
I have these:
alias ls='ls $LS_OPTIONS'
and
LS_OPTIONS='-N --color=tty -T 0'
I inst
6 matches
Mail list logo
