git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] pull: add --hard mode

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 24, 2026, 14:11 UTC
Message-ID
<xmqq1pbntxpe.fsf@gitster.g>
In-Reply-To
<248fc3ca-7907-4720-ab71-1cf5926b82a0@antmicro.com>
Artur Bieniek <abieniek@antmicro.com> writes:
> If resetting does not belong under pull, would the inverse design be 
> more appropriate, e.g. git reset --pull --hard, meaning “fetch the 
> configured upstream and reset to it”? Or would making reset perform 
> network I/O be undesirable for the same reason?

Very true. I wonder if the feature of git you should be looking at for doing things like this is not "pull", "fetch", or "reset" but is "alias"?

Previous: Artur BieniekNext: Junio C Hamano
Message 8 of 9 in “pull: add --hard mode”
  1. pull: add --hard modeArtur Bieniek via GitGitGadget, Aug 18, 2026
  2. Junio C HamanoAug 18, 2026
  3. Phillip WoodAug 20, 2026
  4. Junio C HamanoAug 20, 2026
  5. Artur BieniekAug 20, 2026
  6. Kristoffer HaugsbakkAug 20, 2026
  7. Artur BieniekAug 24, 2026
  8. Junio C HamanoAug 24, 2026
  9. Junio C HamanoAug 21, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.