Hi Chris, On 8 August 2017 at 14:44, Christopher Li <sparse@xxxxxxxxxxx> wrote: > I hope that clear up the git pull situations on sparse-next. If it helps, I can > also rename spase-next to "unstable". I am also open to suggestion for how > this integration should be done. The original intend for having this complex > model is to get rid of the dirty history. If that turn out to be the > bigger evil. I am not sure why you consider some history "dirty". I think all history is good as it tells people how the change evolved, If you apply a patch and a bug is found, or you want to amend the patch somehow, in my view there should simply be another patch or change done following the original rather than trying to backout history and redo the patch. I am not a git expert so I cannot comment on the git processes but conceptually I am saying that all history is good. Regards Dibyendu -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
