Re: [1.8.0] make two-argument fetch update remote branches
- From
Thomas Rast <trast@student.ethz.ch>
- Date
- Feb 1, 2011, 22:39 UTC
- Message-ID
- <201102012339.31684.trast@student.ethz.ch>
- In-Reply-To
- <4D4875B2.4070008@gmail.com>
A Large Angry SCM wrote:
Show 11 quoted lines
> On 01/31/2011 04:44 PM, Thomas Rast wrote:
> >
> > Since the remote branches in some sense reflect the "last known state"
> > of the remote, it would make sense to also update them to whatever a
> > two-argument fetch got.
>
> If this is proposing to break:
>
> get-fetch ${REPO} ${SRC_REF}:${DST_REF}
>
> then I am against this since that form _is_ used and *is* plumbing.You're mixing up the two proposals. This one is to teach
git fetch repo foo
to update refs/remotes/repo/foo with the new value (maybe we should also have it update in the foo:bar case, but I haven't thought that through).
The other one is to forbid 'git pull repo foo:bar' and would not change git-fetch at all.
--
Thomas Rast
trast@{inf,student}.ethz.ch