> > > misc/CTF/record-ctf.ref | 55 > +++++++++++++++++++++++++++++++++---------------- > > We should avoid uppercase or mix case in file names unless they are > existing or > in imported code. We have some hosts that are case insensitive and our > experience over the years is this can cause problems. :) > Okay. I didn't know that. :)
> > Is this file for the rtems-tools repo? Yes > If it is not please ignore the following. > > I wonder if there should be a top level trace directory to gather all the > trace > pieces in one place. I think trace is important enough to have this > status. So > this file could be ... > > trace/config/ctf/record-ctf.ref > > or > > trace/config/record-ctf.ref > It's metadata file for TSDL description. I will rename it to "metadata" > > ? This is only an example as I am not really sure what role this file > plays. > > Notes: > > 1) I have found in other parts of rtems-tools.git having the config > directory of > files separated from the other sources makes installing into the shared > tree > simpler. > > 2) The tools currently in rtems-tools.git can be run with the same command > line > options from a built repo with an absolute path or when installed under a > prefix. This is something to consider when referencing configuration files. > > Okay, Chris. Thanks for the review. -- *Ravindra Kumar Meena*, B. Tech. Computer Science and Engineering, Indian Institute of Technology (Indian School of Mines) <https://www.iitism.ac.in/>, Dhanbad
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
