[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Strange response after merge from upstream
From: |
Óscar Fuentes |
Subject: |
Re: Strange response after merge from upstream |
Date: |
Wed, 02 Dec 2009 18:44:37 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
>> `pull' never merges because there is nothing that can cause conflicts.
>
> Oh, so that's the misconception from which comes the stupid idea
> that --show-base would only apply to merge but not to pull?
>
> FYI, this is not true: it has to merge the incoming patches with the
> local uncommitted changes.
Yes, IMO that feature is so wrong that I forgot about it.
By default, `pull' should refuse to operate if there are local edited
files. If you often work on that scenario, you'll better use a bound
branch and `update' instead of `pull'.
--
Óscar
- Re: Strange response after merge from upstream, (continued)
- Re: Strange response after merge from upstream, Eli Zaretskii, 2009/12/01
- Re: Strange response after merge from upstream, Óscar Fuentes, 2009/12/01
- Re: Strange response after merge from upstream, Eli Zaretskii, 2009/12/02
- Re: Strange response after merge from upstream, Óscar Fuentes, 2009/12/02
- Re: Strange response after merge from upstream, Eli Zaretskii, 2009/12/02
- Re: Strange response after merge from upstream, Stefan Monnier, 2009/12/02
- Re: Strange response after merge from upstream, Eli Zaretskii, 2009/12/02
- Re: Strange response after merge from upstream, Stephen J. Turnbull, 2009/12/02
- Re: Strange response after merge from upstream, Óscar Fuentes, 2009/12/02
- Re: Strange response after merge from upstream, Stefan Monnier, 2009/12/02
- Re: Strange response after merge from upstream,
Óscar Fuentes <=
- Re: Strange response after merge from upstream, Stefan Monnier, 2009/12/02
- Re: Strange response after merge from upstream, Alexander Belchenko, 2009/12/02