The devmanual should explain that when there isn't a changelog in the directory where you are editing some files, you need to run 'cd ..' until you will see a changelog. Good example: gentoo-x86/profiles/arch/powerpc/ppc64 and the changelog is only in gentoo-x86/profiles/arch/powerpc/
Well I don't think it needs further explanation. If you can't see a changelog in the current directory, you just look on the parent dir etc etc. This is the "default" approach. But anyway, if someone wants to write a patch I am fine with it
(In reply to comment #1) > Well I don't think it needs further explanation. If you can't see a > changelog in the current directory, you just look on the parent dir etc etc. > This is the "default" approach. > But anyway, if someone wants to write a patch I am fine with it That's fine, but this default approach is not documented and we need to do it
(In reply to comment #1) > Well I don't think it needs further explanation. If you can't see a > changelog in the current directory, you just look on the parent dir etc etc. > This is the "default" approach. This makes sense in theory, but there are many instances of this not happening from both new and very old devs.
(In reply to comment #3) > (In reply to comment #1) > > Well I don't think it needs further explanation. If you can't see a > > changelog in the current directory, you just look on the parent dir etc etc. > > This is the "default" approach. > > This makes sense in theory, but there are many instances of this not > happening from both new and very old devs. True but I really doubt anyone would look in the devmanual for this. It's better if you just advertise it in the mailing list. Then we can document it.
(In reply to comment #4) > True but I really doubt anyone would look in the devmanual for this. It's > better if you just advertise it in the mailing list. Then we can document it. I know the way to do it, but the bug born because of Micheal's mistake and I guess the advise on the mailing list is wrong. Who will advise a new developer that will join e.g. in June? The documentation needs for a reason.
(In reply to comment #5) > (In reply to comment #4) > > True but I really doubt anyone would look in the devmanual for this. It's > > better if you just advertise it in the mailing list. Then we can document it. > > I know the way to do it, but the bug born because of Micheal's mistake and I > guess the advise on the mailing list is wrong. Who will advise a new > developer that will join e.g. in June? The documentation needs for a reason. It's obvious that I suggested that as a reminder to old developers. Once everyone is aware of that, then we can document it. I prefer it this way instead of going documenting such bits in the devmanual silently.
Well nobody discussed it in the list, so i just fixed in the devmanual http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=f4121175e9bc0d0260bbe399ef39339085afa481
