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

branching and supporting a tagged kernel version

From
Don Zickus <dzickus@gmail.com>
Date
Dec 12, 2005, 21:31 UTC
Message-ID
<68948ca0512121331x13bfb691t62224d02ced04a27@mail.gmail.com>
Hello,

I was trying to see if I can use git for a particular way of supporting a kernel and was hoping for some feedback if this approach would work.

Basically I wanted to branch off of 2.6.14 and support personal patches. However over time I would like to be able to merge in hand-pick commits from upstream.

So my questions (for now) are:
1) what is the easiest way to branch off on a tagged version (in this
case 2.6.14)?  I didn't quite understand what <starting point>
referred to in the git-branch docs.
2) is there a way to get a list of commits from upstream that are not
in my branch and then selectively apply them?  Yes, I understand the
potential merge mess...

Thanks, Don

Next: Junio C Hamano
Message 1 of 4 in “branching and supporting a tagged kernel version”
  1. Don ZickusDec 12, 2005
  2. Junio C HamanoDec 12, 2005
  3. Don ZickusDec 12, 2005
  4. Petr BaudisDec 13, 2005

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.