Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot: package	package/busybox project target/ etc...
Date: Thu, 12 Jul 2007 16:32:41 +0200	[thread overview]
Message-ID: <20070712143240.GA21387@aon.at> (raw)
In-Reply-To: <1184242518.5175.19.camel@elrond.sweden.atmel.com>

On Thu, Jul 12, 2007 at 02:15:18PM +0200, Ulf Samuelsson wrote:
>tor 2007-07-12 klockan 08:25 -0500 skrev Steven J. Hill:
>> For patches like this and the other ones you are doing, I really feel
>> you should be required to update the on-line documentation at the same
>> time to denote all these changes you are making. It's difficult enough
>> to keep up with all of the changes. Please make sure when you add new
>> features like this in the future to not do so unless you document it.
>> Please also document this BSP patch for the on-line docs. Thanks.
>> 
>
>Is there a recommended tool to edit HTML with CSS?

./busybox vi

  parent reply	other threads:[~2007-07-12 14:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 13:11 [Buildroot] svn commit: trunk/buildroot: package package/busybox project target/ etc ulf at uclibc.org
2007-07-12 13:25 ` Steven J. Hill
2007-07-12 11:58   ` Ulf Samuelsson
2007-07-12 12:15   ` Ulf Samuelsson
2007-07-12 14:02     ` Alexander Kriegisch
2007-07-12 14:32     ` Bernhard Fischer [this message]
2007-07-12 14:42 ` Bernhard Fischer
2007-07-12 13:56   ` Ulf Samuelsson
2007-07-12 15:51     ` Yann E. MORIN
2007-07-12 16:24       ` [Buildroot] svn commit: trunk/buildroot: package?package/busybox " Bernhard Fischer
2007-07-12 16:39         ` Yann E. MORIN
2007-07-12 17:51         ` Benjamin Tietz

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=20070712143240.GA21387@aon.at \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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