Jonathan So, for this example: do you think the DESCRIPTION section of
Jonathan git-fetch(1) should be reorganized like git-checkout(1) to
Jonathan describe each form of the command separately?
Yes, except that the case of checkout is so horrifyingly unorthogonal
that it is _really_ hard (maybe
Package: git-man
Version: 1:1.7.9.5-1
Severity: minor
Tags: upstream
What is the behavior of git fetch with no arguments? The manpage
doesn't say (of course you need to parse the manpage carefully to
determine that, grr) and neither is this covered by the other
documentation out there like the
severity 669204 normal
quit
Hi Ian,
Ian Zimmerman wrote:
What is the behavior of git fetch with no arguments? The manpage
doesn't say
Good catch.
Confusingly enough, this stuff is documented in git-pull(1) but
not git-fetch(1)!
Default values for repository and branch are read
Jonathan Confusingly enough, this stuff is documented in git-pull(1)
Jonathan but not git-fetch(1)!
Default values for repository and branch are read from the
remote and merge configuration for the current branch as set by
git-branch --track.
I have never executed git branch --track. In
Ian Zimmerman wrote:
Jonathan Confusingly enough, this stuff is documented in git-pull(1)
Jonathan but not git-fetch(1)!
Default values for repository and branch are read from the
remote and merge configuration for the current branch as set by
git-branch --track.
I have never executed git
5 matches
Mail list logo
