Recommended way to "enumerate" source files for changes?

From	Victor Porton <porton@narod.ru>
Newsgroups	comp.programming
Subject	Recommended way to "enumerate" source files for changes?
Date	2017-09-26 01:00 +0300
Organization	Aioe.org NNTP Server
Message-ID	<oqbu9i$u36$1@gioia.aioe.org> (permalink)

Show all headers | View raw

I have a Git repo with source files.

I decided to review all the files and do certain kind of changes for every 
of these files.

What is the best way to record which files I have already reviewed (and 
rewritten as needed)?

I have the following ideas:

1. Order files alphabetically and store in a TODO.txt (or like this) the 
name of the last file which is not yet processed.

2. Before doing it, add to every source file the comment that this file is 
not reviewed yet. Remove the comment after I finish all these changes with a 
file.

What way (the above or something other) is the best?

--
Victor Porton - http://portonvictor.org

Back to comp.programming | Previous | Next | Find similar | Unroll thread

Thread

Recommended way to "enumerate" source files for changes? Victor Porton <porton@narod.ru> - 2017-09-26 01:00 +0300

csiph-web