On Fri, Aug 02, 2019 at 10:14:28AM +0200, k...@aspodata.se wrote: > Geert Stappers: > > On Thu, Aug 01, 2019 at 12:07:23PM +0200, k...@aspodata.se wrote: > > > So making a data/MANUFACTURERS file like: > > > $ head MANUFACTURERS > > > 00000000001 00000000001 AMD > > > 00000000010 00000000010 AMI > > > 00000000011 00000000011 Fairchild > > > 00000000100 00000000100 Fujitsu > > > 00000000101 00000000101 GTE > > > 00000000110 00000000110 Harris > > > 00000000111 00000000111 Hitachi > > > 00000001001 00000001001 Intel > > > > > > and making theese links (in data directory): > > > 00000000110 -> lexra > > > 00000000111 -> hitachi > > > 00000001001 -> intel/ > > > 00000001110 -> freescale/ > > > 00000010101 -> philips > > > > IMNSHO is that only moving the problem to another place. > > The symlinks add clutter. > > > > It is wrong approach of the challenge of updating data/MANUFACTERS > > Ok, how do you want to handle this then ?
With data/0/PARTS as intermediate step. > To manually update the directory column is a pain that I want to avoid. Pain is a human thing. Yes, updating the directory column will require human attention. Luckly there is no need for a bulk update that might wear down humans. > BTW, I sent you a git format-patch. Regardless if that patch is > accepted or not, is that the way you want possible changes presented ? Yes. Or another form that contains code change plus commit message that can be processed automaticly. Groeten Geert Stappers -- Leven en laten leven _______________________________________________ UrJTAG-development mailing list UrJTAG-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/urjtag-development
