<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lbmk.git/config/git/www, branch 20240612rev2</title>
<subtitle>libreboot build system (LibreBoot MaKe)
</subtitle>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/'/>
<entry>
<title>merge untitled with docs, in releases</title>
<updated>2023-11-03T22:57:55+00:00</updated>
<author>
<name>Leah Rowe</name>
<email>leah@libreboot.org</email>
</author>
<published>2023-11-03T22:57:55+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=dd1e15fd0b8033e5cd2066d04cf49af3ac28b2d7'/>
<id>dd1e15fd0b8033e5cd2066d04cf49af3ac28b2d7</id>
<content type='text'>
with this, you can just do:

cd src/docs

./build

the html files would then be available for
publishing, if you wish, or you could set up
a local httpd to view them.

if you have pandoc installed, this will build the
markdown files into html

untitled static site generator is what generates
the html files, from the markdown files, on the
website. it will now also be included in releases.

Signed-off-by: Leah Rowe &lt;leah@libreboot.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
with this, you can just do:

cd src/docs

./build

the html files would then be available for
publishing, if you wish, or you could set up
a local httpd to view them.

if you have pandoc installed, this will build the
markdown files into html

untitled static site generator is what generates
the html files, from the markdown files, on the
website. it will now also be included in releases.

Signed-off-by: Leah Rowe &lt;leah@libreboot.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Libreboot 20231101</title>
<updated>2023-11-01T16:36:16+00:00</updated>
<author>
<name>Leah Rowe</name>
<email>leah@libreboot.org</email>
</author>
<published>2023-11-01T10:34:05+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=1f1498be7421ae4500ad0d6d40ca0eefbcf8f1a2'/>
<id>1f1498be7421ae4500ad0d6d40ca0eefbcf8f1a2</id>
<content type='text'>
Signed-off-by: Leah Rowe &lt;leah@libreboot.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Signed-off-by: Leah Rowe &lt;leah@libreboot.org&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>config/git/www and www-img: import libreboot.org</title>
<updated>2023-10-21T00:22:26+00:00</updated>
<author>
<name>Leah Rowe</name>
<email>leah@libreboot.org</email>
</author>
<published>2023-10-21T00:22:26+00:00</published>
<link rel='alternate' type='text/html' href='https://browse.libreboot.org/lbmk.git/commit/?id=79c8dc46558cfc271d8c733f3d7c6065c3d4e25b'/>
<id>79c8dc46558cfc271d8c733f3d7c6065c3d4e25b</id>
<content type='text'>
it's not used by anywhere else in lbmk, but the release build
script will automatically download each project named as per
file names in config/git/

this is a stupidly simply way to prove documentation in
libreboot releases, and i've used current revisions corresponding
to the Libreboot 20231021 release, for this 20231021 release
of lbmk.

Signed-off-by: Leah Rowe &lt;leah@libreboot.org&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
it's not used by anywhere else in lbmk, but the release build
script will automatically download each project named as per
file names in config/git/

this is a stupidly simply way to prove documentation in
libreboot releases, and i've used current revisions corresponding
to the Libreboot 20231021 release, for this 20231021 release
of lbmk.

Signed-off-by: Leah Rowe &lt;leah@libreboot.org&gt;
</pre>
</div>
</content>
</entry>
</feed>
