public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: Revision COntrol, Patch Database
Date: Mon, 24 Jan 2005 14:52:15 -0500	[thread overview]
Message-ID: <41F551EF.7060208@smiths-aerospace.com> (raw)
In-Reply-To: <tnxbrbepth9.fsf@arm.com>

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 <gerald.vanbaren@smiths-aerospace.com> 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

  reply	other threads:[~2005-01-24 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4120DD8B.8040709@imc-berlin.de>
2004-10-09 22:20 ` [U-Boot-Users] Re: [PATCH] Cleanup cpu/arm920t using SoC Wolfgang Denk
2004-10-12 14:02   ` [U-Boot-Users] Patch for Cirrus Logic EDB9312 llandre
2005-01-09 23:43     ` Wolfgang Denk
2005-01-18  8:32       ` llandre
2005-01-18  9:28         ` [U-Boot-Users] Revision COntrol, Patch Database -- was: " Wolfgang Denk
2005-01-18  9:59           ` [U-Boot-Users] " llandre
2005-01-18 16:01           ` [U-Boot-Users] " Jerry Van Baren
2005-01-18 21:13             ` Wolfgang Denk
2005-01-18 22:49               ` [U-Boot-Users] Revision COntrol, Patch Database Jerry Van Baren
2005-01-21 17:42                 ` llandre
2005-01-19 10:28               ` [U-Boot-Users] Re: Revision COntrol, Patch Database -- was: Patch for Cirrus Logic EDB9312 Catalin Marinas
2005-01-19 15:56                 ` Jerry Van Baren
2005-01-24 17:14                   ` [U-Boot-Users] Re: Revision COntrol, Patch Database Jerry Van Baren
2005-01-24 18:33                     ` Catalin Marinas
2005-01-24 19:52                       ` Jerry Van Baren [this message]
2005-01-18 14:14         ` [U-Boot-Users] Patch for Cirrus Logic EDB9312 Cliff Brake
2005-01-19  8:33           ` llandre
2005-01-18 15:57         ` Cory Tusar
2005-01-19  8:35           ` llandre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41F551EF.7060208@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox