From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/docs
Date: Thu, 13 Mar 2008 19:25:52 +0100 [thread overview]
Message-ID: <87lk4m5vm7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20080313171631.D6BFF120156@busybox.net> (ninevoltz@uclibc.org's message of "Thu\, 13 Mar 2008 10\:16\:31 -0700 \(PDT\)")
>>>>> "ninevoltz" == ninevoltz <ninevoltz@uclibc.org> writes:
ninevoltz> Author: ninevoltz
ninevoltz> Date: 2008-03-13 10:16:30 -0700 (Thu, 13 Mar 2008)
ninevoltz> New Revision: 21326
ninevoltz> Log:
ninevoltz> add some documentation about buildroot's patch system
ninevoltz> Added:
ninevoltz> trunk/buildroot/docs/patches.html
ninevoltz> Changeset:
ninevoltz> Added: trunk/buildroot/docs/patches.html
ninevoltz> ===================================================================
ninevoltz> --- trunk/buildroot/docs/patches.html (rev 0)
ninevoltz> +++ trunk/buildroot/docs/patches.html 2008-03-13 17:16:30 UTC (rev 21326)
ninevoltz> @@ -0,0 +1,43 @@
ninevoltz> +<!--#include file="header.html" -->
ninevoltz> +
ninevoltz> +<h2>Buildroot patch structure</h2>
ninevoltz> +
ninevoltz> +<p>
ninevoltz> +<h4>Keeping track of applied patches</h4>
ninevoltz> +Whenever a patch is applied to a source code directory in buildroot, a text file named .applied_patches_list is created inside that source directory.
Please try to keep the lines <80 chars like the rest of the
documentation.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2008-03-13 18:25 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 17:16 [Buildroot] svn commit: trunk/buildroot/docs ninevoltz at uclibc.org
2008-03-13 18:25 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-02 10:09 jacmet at uclibc.org
2009-03-02 8:34 jacmet at uclibc.org
2009-02-12 9:33 jacmet at uclibc.org
2009-02-09 16:44 jacmet at uclibc.org
2009-01-31 23:02 jacmet at uclibc.org
2009-01-26 20:26 ulf at uclibc.org
2009-01-23 21:06 jacmet at uclibc.org
2009-01-16 19:45 jacmet at uclibc.org
2009-01-16 21:02 ` Markus Heidelberg
2009-01-16 19:45 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-15 14:50 jacmet at uclibc.org
2009-01-06 16:30 ulf at uclibc.org
2009-01-06 16:34 ` Peter Korsgaard
2008-12-18 0:48 root at uclibc.org
2008-12-16 9:00 jacmet at uclibc.org
2008-12-15 22:35 tpetazzoni at uclibc.org
2008-12-15 22:44 ` Thomas Petazzoni
2008-12-16 9:03 ` Peter Korsgaard
2008-12-16 9:00 ` Peter Korsgaard
2008-12-15 22:14 tpetazzoni at uclibc.org
2008-12-08 8:15 jacmet at uclibc.org
2008-10-14 16:20 aldot at uclibc.org
2008-10-18 6:58 ` Peter Korsgaard
2008-10-06 9:11 jacmet at uclibc.org
2008-06-23 13:40 jacmet at uclibc.org
2007-09-27 21:32 aldot at uclibc.org
2007-09-19 9:08 aldot at uclibc.org
2007-09-02 17:44 aldot at uclibc.org
2007-08-24 5:28 ulf at uclibc.org
2007-08-16 21:54 ulf at uclibc.org
2007-08-12 23:26 ulf at uclibc.org
2007-08-11 21:58 ulf at uclibc.org
2007-08-01 8:11 ulf at uclibc.org
2007-07-12 17:04 ulf at uclibc.org
2007-07-12 16:53 ulf at uclibc.org
2007-07-12 14:46 ulf at uclibc.org
2007-07-12 14:43 ulf at uclibc.org
2007-07-12 15:07 ` Bernhard Fischer
2007-06-21 16:58 aldot at uclibc.org
2007-03-13 12:59 aldot at uclibc.org
2007-01-21 21:49 aldot at uclibc.org
2007-01-19 19:28 aldot at uclibc.org
2007-01-19 19:21 aldot at uclibc.org
2007-01-19 19:20 aldot at uclibc.org
2007-01-19 13:32 aldot at uclibc.org
2007-01-19 12:35 aldot at uclibc.org
2007-01-19 11:00 aldot at uclibc.org
2007-01-19 10:57 aldot at uclibc.org
2007-01-19 9:47 aldot at uclibc.org
2007-01-19 9:24 aldot at uclibc.org
2007-01-17 10:07 aldot at uclibc.org
2006-12-22 12:11 aldot at uclibc.org
2006-11-05 11:21 aldot at uclibc.org
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=87lk4m5vm7.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.