Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

Re: branching and supporting a tagged kernel version

From: Petr Baudis <hidden>
Date: 2016-06-15 22:42:14

Dear diary, on Tue, Dec 13, 2005 at 12:58:38AM CET, I got a letter
where Don Zickus [off-list ref] said that...
Thanks for clearing things up.
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help