From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Mon, 24 Jan 2005 14:52:15 -0500 Subject: [U-Boot-Users] Re: Revision COntrol, Patch Database In-Reply-To: References: <41ED32F0.3020109@smiths-aerospace.com> <20050118211358.6006EC108D@atlas.denx.de> <41EE833D.80802@smiths-aerospace.com> <41F52D04.4080908@smiths-aerospace.com> Message-ID: <41F551EF.7060208@smiths-aerospace.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Catalin Marinas wrote: > I've been using GNU Arch extensively with the Linux kernel and I am > happy with what it can do. I have a minor suggestion below: > > Jerry Van Baren writes: > >>Due to violation of ARCH naming conventions, ARCH has problems >>importing the following U-Boot files >> >>directories: >> >> board/MAI/bios_emulator/scitech/lib/debug/linux/gcc/glibc.so >>board/MAI/bios_emulator/scitech/lib/debug/linux/gcc/libc.so >>board/MAI/bios_emulator/scitech/lib/release/linux/gcc/glibc.so >>board/MAI/bios_emulator/scitech/lib/release/linux/gcc/libc.so > > > You should usually import a clean source to avoid adding > compiler-generated files to the repository. Arch tries to ensure some > discipline on what files are kept in the working directory (but this > can be modified to be a simple warning, not an error). > > You can ignore them by changing the "unrecognized" regexp in the > {arch}/=tagged-method file and it or by adding .arch-inventory files > in those directories. > > Catalin FWIIW, I did start with clean source. Those directories are in the u-boot tree and contain a readme.txt file that states "This file is just to ensure that the directory is created." I'll have to use your .arch-inventory tip to avoid the problem for my purposes, but this isn't going to work for someone that cares about MAI bios emulators :-/. Thanks, gvb