They need to be merged separately too since the author is often different on each patch.If they are related / dependent on each other, then I think those kinds of patchsets should be encapsulated in one branch.The need to be applied and committed in sequence. Sometimes the final patch is the one that fixes the coding style. This is inherently very manual.
- RE:Software release life cycle choices could have imp... David Sidrane
- Re: Software release life cycle choices could have im... Nathan Hartman
- Re: Software release life cycle choices could ha... Gregory Nutt
- Re: Software release life cycle choices coul... Gregory Nutt
- Re: Software release life cycle choices ... Nathan Hartman
- RE: Software release life cycle choices ... David Sidrane
- Re: Software release life cycle choices ... Gregory Nutt
- RE: Software release life cycle choices ... David Sidrane
- Re: Software release life cycle choices ... Nathan Hartman
- Re: Software release life cycle choices ... Gregory Nutt
- Re: Software release life cycle choices ... Gregory Nutt
- Re: Software release life cycle choices ... Brennan Ashton
- Re: Software release life cycle choices ... Duo Zhang
- Re: Software release life cycle choices ... Justin Mclean
- Re: Software release life cycle choices ... Xiang Xiao
- Re: Software release life cycle choices ... Duo Zhang
- Re: Software release life cycle choices ... Justin Mclean
- Re: Software release life cycle choices ... Xiang Xiao
- Re: Software release life cycle choices ... Duo Zhang
- Re: Software release life cycle choices ... Abdelatif Guettouche
- Re: Software release life cycle choices ... David Sidrane