Re: how to track the history of a line in a file
- From
- david@lang.hm <david@lang.hm>
- Date
- Jan 2, 2009, 22:58 UTC
- Message-ID
- <alpine.DEB.1.10.0901021455390.21567@asgard.lang.hm>
- In-Reply-To
- <3ab397d0901021349h4ebae0c1g460a0c8abd4ec072@mail.gmail.com>
On Fri, 2 Jan 2009, Jeff Whiteside wrote:
Show 14 quoted lines
>> -oldline >> +newline >> >> it's a 1-1 correspondence >> >> if it's instead >> -oldline1 >> -oldline2 >> +newline1 >> +newline2 > > what a neat idea. i'm going to start malloc'ing 10,000 lines x 120 > chars for each file i add, and edit them so that no new lines replace > removed lines unless it's intended that they were the same line.
I don't understand your comment. that isn't nessasary to do the tracking that I'm needing (you don't have to look at every line, only some of the lines that are in the same hunk of the patch as the line(s) you are interested in)
in my situation the use case is config files. in them each line is usually edited independantly of other lines (with stuff being added, usually, but not always on the end)
David Lang