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

merging initial part of a branch?

From
JFJ. Bruce Fields <bfields@fieldses.org>
Date
Jan 11, 2006, 23:04 UTC
Message-ID
<20060111230451.GH8618@fieldses.org>

External kernel projects sometimes work only against major releases--it's easier for their users/testers to find a major release than a random git version, and at least in the early prototype stage, it isn't critical to be working on the tip all the time.

Is there a simple way to say, for example, "merge in all the upstream changes up to v2.6.15"?

It looks like git pull will only update me to the very tip of a branch. I could create a new local branch that stops at v2.6.15, then pull from that. Can I accomplish the same thing somehow with just one git pull? Or is there some other convenient shorthand that I've missed?

--b.
Next: Junio C Hamano
Message 1 of 17 in “merging initial part of a branch?”
  1. J. Bruce FieldsJan 11, 2006
  2. Junio C HamanoJan 11, 2006
  3. Andreas EricssonJan 12, 2006
  4. Junio C HamanoJan 12, 2006
  5. Andreas EricssonJan 12, 2006
  6. J. Bruce FieldsJan 12, 2006
  7. J. Bruce FieldsJan 12, 2006
  8. Junio C HamanoJan 12, 2006
  9. J. Bruce FieldsJan 13, 2006
  10. Junio C HamanoJan 13, 2006
  11. J. Bruce FieldsJan 13, 2006
  12. Junio C HamanoJan 13, 2006
  13. J. Bruce FieldsJan 13, 2006
  14. Junio C HamanoJan 15, 2006
  15. J. Bruce FieldsJan 16, 2006
  16. Junio C HamanoJan 16, 2006
  17. J. Bruce FieldsJan 23, 2006

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.