Automated patch porting across forked projects

Abstract

Forking projects provides a straightforward method for developers to reuse existing source code and tailor it to their own application scenarios, which can significantly reduce developers' burden. However, this process makes forked projects (upstream projects and their forks) share the same defects on reused code as well. With the independent development of forked projects, some defects can only be repaired in one of them, where the patches need to be ported to others as well. Manually tracking all such activities among them is hard. Previous studies reveal that porting patches across forked projects is imperative and call research in this direction. Targeting at this problem, we conducted an empirical study to analyze the characteristics of patches in forked projects. We found that 20.5% patches need to be ported among all analyzed patches, which is a non-negligible portion. Among all those patches that need to be ported, 73.2% can be easily ported by simple syntactic code transformations. However, it is still challenging for other 26.8% patches since the corresponding code has experienced different modifications in the forked projects. As a result, according to the insights from the study, we proposed a new approach, which aims to automatically identify and port patches across forked projects.

BibTeX

@inproceedings{Ren:FSE19,
  author    = {Luyao Ren},
  title     = {Automated patch porting across forked projects},
  booktitle = {{ESEC/SIGSOFT} {FSE}},
  pages     = {1199--1201},
  publisher = {{ACM}},
  year      = {2019},
}

Automated patch porting across forked projects

Abstract

Related papers