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

Re: branching and supporting a tagged kernel version

From
Petr Baudis <pasky@suse.cz>
Date
Dec 13, 2005, 00:01 UTC
Message-ID
<20051213000140.GZ22159@pasky.or.cz>
In-Reply-To
<68948ca0512121558s6e300103t95fcc0e9573604a7@mail.gmail.com>

Dear diary, on Tue, Dec 13, 2005 at 12:58:38AM CET, I got a letter where Don Zickus <dzickus@gmail.com> said that...

Show 10 quoted lines
> Thanks for clearing things up.
> 
> > I'll refrain from saying that it is not the usual way to work
> > with git, since you seem to know what you are doing.  So let's
> 
> Either this or cvs. :)  Anyway my work involves releasing a platform
> to customers who don't want  to constantly upgrade their kernel.  And
> instead of waiting for bugs to be filed, I was just trying to find a
> way to be pro-active and fix certain bugs _before_ our customers hit
> them.

You might also consider managing your patches in StGIT, which could give you more comfort for managing them. StGIT provides quilt-like functionality on top of GIT, and it's easy to reorder, add, and remove patches, as well as submit them to the upstream and remove them automatically when they get merged.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Don Zickus
Message 4 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.