This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> Actually this was copied from powerpc32, which still uses the > dl_reloc_overflow symbol dl-machine.c, but that is OK because it is static? Yes, the names of static functions don't matter (except their readability). > So in the case of copying files into new directory (while slight > modifications), when should I include whole copywrite pedigree and when > should I just specify the release year? It's always safe to keep the old copyright years. I sometimes remove old ones and just insert this year when adding a new file, but usually not when there is a great deal copied from the old file. Of course, when there is a whole lot copied it's often a sign that the plan is wrong and something should be done to share more code and copy less.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |