From: Christos Trochalakis <yatiohi@ideopolis.gr>
To: git list <git@vger.kernel.org>
Subject: Maintaining an html branch
Date: Tue, 25 May 2010 09:43:22 +0300 [thread overview]
Message-ID: <AANLkTimMVn8fMVBmfNi4vR3kk3cXF2gq0Y9Ij5w3cl15@mail.gmail.com> (raw)
Hello,
I would like to maintain an html branch for my repo, containing files
under my '_site/' dir that is not version controlled.
Below is a first draft that works, but as I am not really familiar
with git plumbing, I'd appreciate any comments on a better way or
style to to write it.
#!bash
jekyll --no-auto # build the static website on _site/ dir
rm .git/html.index
export GIT_INDEX_FILE=.git/html.index
git add -f _site
tree_id=$(git write-tree --prefix=_site/)
new_commit=$(echo "New website"|git commit-tree $tree_id -p html)
git update-ref html $new_commit
rm .git/html.index
Thanks,
Chris
next reply other threads:[~2010-05-25 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 6:43 Christos Trochalakis [this message]
2010-05-25 19:21 ` Maintaining an html branch Jonathan Nieder
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=AANLkTimMVn8fMVBmfNi4vR3kk3cXF2gq0Y9Ij5w3cl15@mail.gmail.com \
--to=yatiohi@ideopolis.gr \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).