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

Re: [PATCH 0/5] ff-refs: builtin command to fast-forward local refs

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Nov 17, 2015, 15:28 UTC
Message-ID
<564B47AC.7070609@drmicha.warpmail.net>
In-Reply-To
<CANoM8SWxMeDjwy-GwVc+En8D7N8LyzzsBKtX_MbiS4Z49DjD7g@mail.gmail.com>
Mike Rappazzo venit, vidit, dixit 17.11.2015 14:58:
> (This message is off list)
[cut the message part, though no big secrets there]
Hi Mike,
I don't think there's a point in discussing this off-list.
Your intentions are clearer now, yes, or else I would have asked more.

I still don't like the idea of having a new command just for the purpose of fast-forwarding local branches from specified upstreams.

What's wrong with "git merge --ff-only" once you check them out? We have all the gory messages when you checkout a branch or use the git prompt or "branch -vv". And if you don't - how is forgetting to "ff-refs" better than forgetting to "merge --ff-only"?

In short, I don't see a problem that this is solving, but maybe it's because we use local branches differently, I dunno.

If other people were interested they should or would have come up with comments, I think (as a general rule).

Cheers, Michael

Previous: Mike RappazzoNext: Mike Rappazzo
Message 9 of 13 in “ff-refs: builtin command to fast-forward local refs”
  1. 0/5 ff-refs: builtin command to fast-forward local refsMichael Rappazzo, Nov 11, 2015
  2. 1/5 ff-refs: builtin cmd to check and fast forward local refs to their upstreamMichael Rappazzo, Nov 11, 2015
  3. 2/5 ff-refs: update each updatable refMichael Rappazzo, Nov 11, 2015
  4. 3/5 ff-refs: add --dry-run and --skip-worktree optionsMichael Rappazzo, Nov 11, 2015
  5. 4/5 ff-refs: Add documentationMichael Rappazzo, Nov 11, 2015
  6. 5/5 ff-refs: Add testsMichael Rappazzo, Nov 11, 2015
  7. Michael J GruberNov 11, 2015
  8. Mike RappazzoNov 11, 2015
  9. Michael J GruberNov 17, 2015
  10. Mike RappazzoNov 17, 2015
  11. Johannes SchindelinNov 18, 2015
  12. Jeff KingNov 24, 2015
  13. Junio C HamanoDec 1, 2015

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.