Browse Prior Art Database

A method to get the history of code changes done on a given code fragment

IP.com Disclosure Number: IPCOM000199938D
Publication Date: 2010-Sep-21
Document File: 2 page(s) / 46K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article discloses a method to automatically get the history of the code changes done on a given code segment. Using the disclosed method a user would be able to quickly pull out all the modifications done to a code fragment and refer to them in one place.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 100% of the total text.

Page 1 of 2

A method to get the history of code changes done on a given code fragment

When working on a bug, developers need to gain perspective on the code
fragments to understand the problem at hand and before proposing a
fix. They need to understand as to why a particular piece of code was
introduced or altered. This knowledge is important to understand the
historical perspective of the issue at hand, because the old check-ins
contains valuable comments and insights. This article discloses a
method to automatically get the history of the code changes done on a
given code segment. Using the disclosed method a user would be able to
quickly pull out all the modifications done to a code fragment and
refer to them in one place.

To get the history of a given code fragment, an option would be
provided in the version control systems where in user can highlight a
code fragment and right click on the selected code. Then the user
would choose option "show history". The tool will then automatically
go thru the history of the selected fragment and list out all the
check-ins that have introduced/altered the code fragment in question
for ready referral.

The disclosed solution would be implemented as follows:

1

Page 2 of 2

2

[This page contains 1 picture or other non-text object]