public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Stand alone app for changing MAC address in SMC91C111
Date: Fri, 15 Oct 2004 00:21:19 +0200	[thread overview]
Message-ID: <87d5zlq6u8.fsf@deepthought.outer.space.org> (raw)
In-Reply-To: <6.1.1.1.0.20041013074138.01e2a508@wheresmymailserver.com> (Robin Getz's message of "Wed, 13 Oct 2004 07:59:18 -0700")

Hi,

> Based on people's feedback, I will submit as a patch to this list.
>
> One questions:
> 1) should READMEs for stand-alone applications stay in the examples
>     dir, or go in the doc directory?

There are good reasons for both - but I would vote for leaving them in
the examples dir.  That's where I first find out about the examples
and I sure notice some docs sticking in the same directory.  So why
move the docs away as long as there's only one doc per example?

Of course that's only my personal viewpoint but I guess you also asked
for those ;)

Cheers
  Detlev

-- 
five monkeys, two typewriters, ten minutes

  reply	other threads:[~2004-10-14 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 14:59 [U-Boot-Users] Stand alone app for changing MAC address in SMC91C111 Robin Getz
2004-10-14 22:21 ` Detlev Zundel [this message]
2005-01-12  0:30 ` Wolfgang Denk

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=87d5zlq6u8.fsf@deepthought.outer.space.org \
    --to=dzu@denx.de \
    --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