Re: maint

kp kirchdoerfer <[email protected]>
Newsgroups gmane.linux.leaf.devel
Organization none
Message-ID <1963950.Pm2h97lP6o@stalker>
Hi Erich;

Am Sonntag, 4. Oktober 2015, 22:23:12 schrieb Erich Titl:
> Hi Folks
> 
> I am a bit puzzled how I should proceed with stuff I am doing in maint.
> I would like to have my contributions going into it, but I am constantly
> being thrown out of sync by what I would call intrusive changes in that
> branch. I consider kernel changes intrusive, as it makes recompilation
> and tests impossible when the underlying kernel changes often. I could,
> of course, branch off and be done with it, but then my changes would not
> be available to others to test.

You definition of "intrusive" is from the view of the build environment. From 
the view of a production environment kernel updates are just more or less 
important bugfixes and security fixes. Note that usually such kernel updates are 
introduced this way: "I'm announcing the release of the 4.1.10 kernel. All 
users of the 4.1 kernel series must upgrade" by the maintainer. So it's inline 
with our goals for branch maint.
 

> I believe the current setting needs some refinement. I have quite some
> experience with linear code management systems, but git is a completely
> different beast.
> 
> Here just my experience with 5.2
> 
> I needed to recompile some kernel code but without me noticing kernel
> has moved from 4.1.7 to  4.1.8 and 4.1.9. I consider these changes quite
> intrusive as it makes it very hard to work on single, possibly kernel
> version related issues when the kernel version changes constantly under
> your feet. Basically this means I cannot work on maint and I have to
> branch off but then I am cut off the new stuff happening on maint. I
> don't see the way out of this impasse but stopping to call things maint
> when in fact this is just ongoing work on a future environment.
> 
> Let me know how to overcome this.

As you said  yourself: Create a branch locally, work on your changes and merge 
back into maint if done. If you think your work needs more testing by others 
make your branch available remotely.

kp

------------------------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.