Re: git pull --no-ff documentation

2012-10-01 Thread Junio C Hamano
"Philip Oakley" writes: >> This actually is not about --no-ff but about --no-tags. Any option >> that "pull" itself does not care about stops the command line parser >> and the remainder of the command line is fed to underlying "fetch". >> > > Should this be said within the documentation's synop

Re: git pull --no-ff documentation

2012-10-01 Thread Philip Oakley
From: "Junio C Hamano" 乙酸鋰 writes: The order of options in git pull is not clear in the documentation It only says git pull [options] [ [...]] So we have no idea which options should come first I tried git pull -v --no-tags --progress --no-ff origin but failed with unknown option 'no-ff'. B

Re: git pull --no-ff documentation

2012-09-30 Thread Junio C Hamano
乙酸鋰 writes: > The order of options in git pull is not clear in the documentation > It only says > git pull [options] [ [...]] > So we have no idea which options should come first > > I tried > git pull -v --no-tags --progress --no-ff origin > but failed with unknown option 'no-ff'. > > But if I r

git pull --no-ff documentation

2012-09-30 Thread 乙酸鋰
Hi, The order of options in git pull is not clear in the documentation It only says git pull [options] [ [...]] So we have no idea which options should come first I tried git pull -v --no-tags --progress --no-ff origin but failed with unknown option 'no-ff'. But if I ran git pull -v --no-ff --n