Put public headers in include/ instead of src/ about gflags HOT 4 CLOSED

Interesting -- that's not an organization I've seen before, though maybe I'm 
more
typically looking at binaries rather than libraries.  In any case, our setup to
package and distribute packages uses the current structure, which honestly I'm 
not so
bothered by, so I'm going to close this WillNotFix.

It is very common in libraries. I just checked a few packages and for example 
SDL, 
libxml2, FreeType and the Linux kernel put their public header files in a 
directory 
named "include" in the source tree. Because gflags is a very compact code base, 
the 
only private header file it has is "config.h", but when it grows, please 
reconsider 
separating the public headers.

I must be misunderstanding something.  The public headers are separated: 
they're all
in src/gflags (which private headers are elsewhere in src).  I guess you're just
saying they're not separated in a way that it's clear they're public header 
files? 
In any case, I will keep your suggestion in mind.

Yes, that is exactly what I mean: they are currently nicely separated into a 
subdirectory of "src", but I think it would be clearer if they were:
a) separated at the top level
b) in a directory with a name ("include") that is familiar to a lot of people