Re: unclear documentation of git fetch --tags option and tagopt config

2012-12-13 Thread Junio C Hamano
乙酸鋰 ch3co...@gmail.com writes: With git fetch --tags or remote.origin.tagopt = --tags git fetch only fetches tags, but not branches. Current documentation does not mention that no branches are fetched / pulled when --tags option or remote.origin.tagopt = --tags is specified. In the

Re: unclear documentation of git fetch --tags option and tagopt config

2012-12-13 Thread Philip Oakley
From: Junio C Hamano gits...@pobox.com Sent: Thursday, December 13, 2012 6:44 PM 乙酸鋰 ch3co...@gmail.com writes: With git fetch --tags or remote.origin.tagopt = --tags git fetch only fetches tags, but not branches. Current documentation does not mention that no branches are fetched / pulled

Re: unclear documentation of git fetch --tags option and tagopt config

2012-12-13 Thread Junio C Hamano
Philip Oakley philipoak...@iee.org writes: What would be the best way of updating the documentation to clarify the point? Given ch3cooli's previous surprise. Oh, thanks for bringing it up. I was about to start another message that begins with Having said all that... ;-) I think the entire

unclear documentation of git fetch --tags option and tagopt config

2012-12-12 Thread 乙酸鋰
Hi, With git fetch --tags or remote.origin.tagopt = --tags git fetch only fetches tags, but not branches. Current documentation does not mention that no branches are fetched / pulled when --tags option or remote.origin.tagopt = --tags is specified. Regards, ch3cooli -- To unsubscribe from this