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

Re: [PATCH v6 0/4] Add --base option to git-format-patch to record base tree info

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 26, 2016, 18:05 UTC
Message-ID
<xmqqlh40gs9o.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAGZ79kajpAtbHaKLaLHN5+qUOvBofFs-q-vUYWua49GWK7FO9Q@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 15 quoted lines
>     git checkout origin/master
>     # toy around, do stuff
>     git checkout -b new-shiny-feature
>     git format-patch origin-master..
>
> Now I have set the format.useautobase option and then the `git format-patch`
> fails with
>
>     fatal: Failed to get upstream, if you want to record base commit
> automatically,
>     please use git branch --set-upstream-to to track a remote branch.
>     Or you could specify base commit by --base=<base-commit-id> manually.
>
> but as I indicated I want patches from origin/master onwards,
> Could we make use of that information?
As you indicated where other than in this e-mail?  

I think the way for you to indicate that desire expected by this series is to use "git branch" to set upstream of new-shiny-feature branch to origin/master. Shouldn't that work, or is that too much work?

Previous: Stefan BellerNext: Stefan Beller
Message 8 of 16 in “Add --base option to git-format-patch to record base tree info”
  1. 0/4 Add --base option to git-format-patch to record base tree infoXiaolong Ye, Apr 26, 2016
  2. 1/4 patch-ids: make commit_patch_id() a public helper functionXiaolong Ye, Apr 26, 2016
  3. 2/4 format-patch: add '--base' option to record base tree infoXiaolong Ye, Apr 26, 2016
  4. 3/4 format-patch: introduce --base=auto optionXiaolong Ye, Apr 26, 2016
  5. 4/4 format-patch: introduce format.useAutoBase configurationXiaolong Ye, Apr 26, 2016
  6. Stefan BellerApr 26, 2016
  7. Stefan BellerApr 26, 2016
  8. Junio C HamanoApr 26, 2016
  9. Stefan BellerApr 26, 2016
  10. Junio C HamanoApr 26, 2016
  11. Stefan BellerApr 26, 2016
  12. Junio C HamanoApr 26, 2016
  13. Ye XiaolongApr 27, 2016
  14. Junio C HamanoApr 27, 2016
  15. Stefan BellerApr 27, 2016
  16. Stefan BellerApr 26, 2016

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.