Re: Why is there no force pull?
- From
- Christoph Böhmwalder <christoph@boehmwalder.at>
- Date
- Jun 9, 2018, 20:25 UTC
- Message-ID
- <20180609202553.dvoirez5mi2r4ctk@christoph-lap>
- In-Reply-To
- <CABPp-BG9HQ4O8h7-b4oL7KLu+boe6-QV1fvcfW_4O3Rax3W_Hw@mail.gmail.com>
On Sat, Jun 09, 2018 at 01:04:30PM -0700, Elijah Newren wrote:
Show 10 quoted lines
> Upon reading the subject and before reading the body, I assumed you > were going to ask for a 'git pull --force' that would throw away > *uncommitted* changes (i.e. do a 'git reset --hard HEAD' before the > rest of the pull). But then you asked for both uncommitted and > committed changes to be thrown away. That difference isn't something > you have to consider with a push. > > That might be a reason such an option would be confusing, or it might > just be a warning to document the option carefully. Anyway, thought > I'd mention it.
Interesting, I hadn't taken that first scenario into consideration at all. So I guess two very aptly named flags would be necessary to implement this kind of feature...
-- Regards, Christoph