Re: Restraining git pull/fetch to the current branch

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Julian Phillips <julian@...>
Cc: <git@...>
Date: Thursday, January 11, 2007 - 8:59 pm

Julian Phillips <julian@quantumfyre.co.uk> wrote:

No, but fortunately bash has a fancy alias tool:

	alias gp='git pull origin $(git symbolic-ref HEAD)'

perhaps your shell can help.  :-)


Life is going to be painful with that repository with current Git
(1.5.0 and later) as the new default configuration for a clone is to
copy every branch into refs/remotes/origin/*, where * is wildcarded
against the current set of branches on the remote repository.
If that takes "a long time" you will be processing a lot of refs
you don't care about (or need to care about).

-- 
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Restraining git pull/fetch to the current branch, Julian Phillips, (Thu Jan 11, 5:47 pm)
Re: Restraining git pull/fetch to the current branch, Junio C Hamano, (Thu Jan 11, 9:09 pm)
Re: Restraining git pull/fetch to the current branch, Julian Phillips, (Fri Jan 12, 10:08 am)
Re: Restraining git pull/fetch to the current branch, Julian Phillips, (Mon Jan 15, 9:06 am)
Re: Restraining git pull/fetch to the current branch, Shawn O. Pearce, (Thu Jan 11, 8:59 pm)