From: Jonathan Nieder <jrnieder@gmail.com>
To: Christos Trochalakis <yatiohi@ideopolis.gr>
Cc: git list <git@vger.kernel.org>
Subject: Re: Maintaining an html branch
Date: Tue, 25 May 2010 14:21:11 -0500 [thread overview]
Message-ID: <20100525192111.GA7279@progeny.tock> (raw)
In-Reply-To: <AANLkTimMVn8fMVBmfNi4vR3kk3cXF2gq0Y9Ij5w3cl15@mail.gmail.com>
Hi Christos,
Christos Trochalakis wrote:
> I would like to maintain an html branch for my repo, containing files
> under my '_site/' dir that is not version controlled.
[...]
> rm .git/html.index
> export GIT_INDEX_FILE=.git/html.index
[...]
Looks reasonable. Way I suggest a simpler way?
If your goal is to publish an html branch with the rest of your
branches, I would recommend using a separate local repository that
pushes to the same remote repository[1].
If the goal is to stay under draconian disk quotas by not maintaining
two local repositories, one with the web site checked out all the
time, I suggest using contrib/workdir/git-new-workdir.
Hope that helps,
Jonathan
[1] See http://thread.gmane.org/gmane.comp.version-control.git/142831/focus=142865
for an example.
prev parent reply other threads:[~2010-05-25 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 6:43 Maintaining an html branch Christos Trochalakis
2010-05-25 19:21 ` Jonathan Nieder [this message]
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=20100525192111.GA7279@progeny.tock \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=yatiohi@ideopolis.gr \
/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).