This is the mail archive of the gdb@sourceware.org mailing list for the GDB 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] |
On Wednesday 21 March 2012 16:00:29 Stan Shebs wrote: > On 3/19/12 5:48 PM, Mike Frysinger wrote: > > i'd like to split up a ChangeLog to push arch-specific pieces into > > subdirs rather than having the common ChangeLog be clogged with > > non-common changes. is there a policy governing this ? or should i just > > cut all the relevant pieces out of the common one and paste it into the > > subdir and be done ? > > That's a decision left up to maintainers. In general, I've come to > favor having fewer ChangeLog files, as with the ubiquity of public > source-control systems, the manually-maintained logs are coming to seem > more like an anachronism left over from pre-Internet days, and reducing > the number is one way to spend less time and effort on managing them. > Also, if you do per-arch logs, then you've forced everybody making a > cross-arch change into editing dozens of ChangeLogs. So while as > cross-platform types, we love to separate things into subdirs, I think > this is one case where it will come to seem like more of a nuisance than > a benefit. in the case of sim tests, i don't think so. it's uncommon to get updates that span multiple arches in there when compared to the number of arch-specific entries. i think i saw one or two that spanned multiple dirs during the split. certainly YMMV. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |