From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v2] docs: prepare moving the website
Date: Sun, 25 Jan 2015 15:26:33 +0100 [thread overview]
Message-ID: <20150125152633.4e5fb396@free-electrons.com> (raw)
In-Reply-To: <80599fbbc0b35a4caec0ce971940322c388cd3a3.1422054324.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sat, 24 Jan 2015 00:05:54 +0100, Yann E. MORIN wrote:
> This commit just creates a symlink so the website is now accessible from
> both docs/ and docs/website/.
>
> This allows us to have the website now officially in docs/website, while
> still keep backward compatibility with the current scripts that update
> the website. Once those scripts have been updated, we'll be able to truly
> move the website to docs/website/ for good.
>
> All without any perceived downtime or missed updated on the website! :-)
>
> After an idea from Peter.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Peter Korsgaard <jacmet@uclibc.org>
> Acked-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Applied, thanks.
Let's wait for this commit to be picked up by the server, change the
server configuration, and apply the second commit. Let me know when it
is OK to apply the second commit in this series.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-25 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 23:05 [Buildroot] [PATCH 0/2 v2] docs: move website to its own sub-dir (branch yem/website) Yann E. MORIN
2015-01-23 23:05 ` [Buildroot] [PATCH 1/2 v2] docs: prepare moving the website Yann E. MORIN
2015-01-25 14:26 ` Thomas Petazzoni [this message]
2015-01-23 23:05 ` [Buildroot] [PATCH 2/2 v2] docs: really move " Yann E. MORIN
2015-01-25 17:17 ` Thomas Petazzoni
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=20150125152633.4e5fb396@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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