Re: git fetch documentation

2013-06-01 Thread Ramkumar Ramachandra
Nicolas Richard wrote: > - A '*' can be used both in src and dest, and it matches any name, > including subdirectories, but not partial names (i.e. refs/heads/foo* > is invalid). > - multiple fetch lines can be given in .git/config, each of them will be > obeyed > > These are probably obvious

git fetch documentation

2013-06-01 Thread Nicolas Richard
Hello, Regarding the git-fetch man page (IIUC, in pull-fetch-param.txt), in particular the explanation, I feel that two facts are missing: - A '*' can be used both in src and dest, and it matches any name, including subdirectories, but not partial names (i.e. refs/heads/foo* is invalid). - m

Re: git fetch documentation problem or bug

2012-10-21 Thread Junio C Hamano
Drew Northup writes: > On Mon, Oct 8, 2012 at 7:33 PM, Junio C Hamano wrote: >> Junio C Hamano writes: >> >> I personally do not think the downside of breaking backward >> compatibility is too bad. If we do this only when we already are >> configured to keep remote tracking branch for branch $

Re: git fetch documentation problem or bug

2012-10-21 Thread Drew Northup
On Mon, Oct 8, 2012 at 7:33 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> In other words, you can do this from the command line if you want >> to do the update. >> >> $ git fetch origin master:refs/remotes/origin/master > > Now having said all that, we should probably revisit this and

Re: git fetch documentation problem or bug

2012-10-08 Thread Nguyen Thai Ngoc Duy
On Tue, Oct 9, 2012 at 6:33 AM, Junio C Hamano wrote: > * Unify pathspec semantics > >This has happened and commands that used to take only path prefix >style pathspecs now take globs as well [ND] I've been thinking about it lately and will probably restart soon with a different approach

Re: git fetch documentation problem or bug

2012-10-08 Thread Junio C Hamano
Junio C Hamano writes: > In other words, you can do this from the command line if you want > to do the update. > > $ git fetch origin master:refs/remotes/origin/master Now having said all that, we should probably revisit this and possibly other issues and for the ones we can reach concensus, s

Re: git fetch documentation problem or bug

2012-10-08 Thread Junio C Hamano
Junio C Hamano writes: > Angelo Borsotti writes: > >> git fetch does not create the remote refs in >> the current (local) >> repository... >> However, if a git fetch origin is executed, the refs are properly created: > > Working as designed and documented. > > $ git fetch origin master > > is

Re: git fetch documentation problem or bug

2012-10-08 Thread Junio C Hamano
Angelo Borsotti writes: > git fetch does not create the remote refs in > the current (local) > repository... > However, if a git fetch origin is executed, the refs are properly created: Working as designed and documented. $ git fetch origin master is giving the refspec "master" from the com