[cfe-dev] Clang-tidy and version control software
Eugene Zelenko via cfe-dev
cfe-dev at lists.llvm.org
Sun Mar 6 12:13:05 PST 2016
Probably running Clang-tidy with option ti fix problem in headers will
benefit most suggested feature, since it's hard to predict which
headers are affected.
On Sun, Mar 6, 2016 at 7:36 AM, David Blaikie <dblaikie at gmail.com> wrote:
> Cheesy as it is, when I've had to deal with tools like this, I've just
> marked all files as open, done the changes, then unopened any files that
> didn't have changes (or, some tools like this have an option to force write
> a file that's not open, then to list the files that have changes but aren't
> open - so simply pipe that list to the open command)
> But yeah, may not be applicable to all such environments, and either option
> is hardly 'clean'
> On Mar 4, 2016 9:20 AM, "Eugene Zelenko via cfe-dev"
> <cfe-dev at lists.llvm.org> wrote:
> My work code base is stored in ClearCase, and files need to be checked
> out before making changes. This need to be done before allowing
> Clang-tidy to do automatic fixes.
> My previous work database used CVS set up in such way, so write
> permission need to be added manually.
> I think will be good idea to provide possibility in CLang-tidy to call
> arbitrary script with file name as parameter which will make necessary
> preparation steps in version control software before making changes in
> this particular file.
> Other tools like Include What You Use or Clazy could benefit from this too.
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
More information about the cfe-dev