Abstract
This paper presents an algorithm for computing a change log for an element whose history includes merges. A change log is a list of comments corresponding to versions “between” two selected versions. For example, a user may want to know what changes were made to element foo.c, between the versions labeled Release1 and Release2.
This is a preview of subscription content, log in via an institution to check access.
Preview
Unable to display preview. Download preview PDF.
References
Atria, Inc. ClearCase Concepts Manual, 1992.
Atria, Inc. ClearCase Reference Manual, 1992.
W. Babich. Software Configuration Management. Addison-Wesley, 1986.
Hewlett-Packard Company. HP-UX Reference, Release 9.0, 1992.
Hewlett-Packard Company. Programming on HP-UX, Release 9.0, 1992.
E. Horowitz and S. Sahni. Fundamentals of Data Structures. Computer Science Press, 1982.
M. Rochkind. The source code control system. IEEE Transactions on Software Engineering, pages 364–370, December 1975.
W. Tichy. RCS: A system for version control. Software: Practice and Experience, 15(7):637–654, July 1985.
D. Whitgift. Methods and Tools for Software Configuration Management. Wiley, 1991.
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1997 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Buffenbarger, J., Gruell, K. (1997). What have you done for me lately? (Branches, merges, and change logs). In: Conradi, R. (eds) Software Configuration Management. SCM 1997. Lecture Notes in Computer Science, vol 1235. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-63014-7_2
Download citation
DOI: https://doi.org/10.1007/3-540-63014-7_2
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-63014-2
Online ISBN: 978-3-540-69063-4
eBook Packages: Springer Book Archive