Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming > #8053 > unrolled thread

Recommended way to "enumerate" source files for changes?

Started byVictor Porton <porton@narod.ru>
First post2017-09-26 01:00 +0300
Last post2017-09-26 01:00 +0300
Articles 1 — 1 participant

Back to article view | Back to comp.programming


Contents

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

#8053 — Recommended way to "enumerate" source files for changes?

FromVictor Porton <porton@narod.ru>
Date2017-09-26 01:00 +0300
SubjectRecommended way to "enumerate" source files for changes?
Message-ID<oqbu9i$u36$1@gioia.aioe.org>
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

[toc] | [standalone]


Back to top | Article view | comp.programming


csiph-web