From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: updating only changed files source directory?
Date: Tue, 24 Oct 2006 09:48:39 +0200 [thread overview]
Message-ID: <ehkgfs$af6$1@sea.gmane.org> (raw)
In-Reply-To: ehjqgf$ggb$1@sea.gmane.org
Han-Wen Nienhuys wrote:
> I have some questions and remarks
I see that you are using fairly low level commands (plumbing commands)
> git-http-fetch -a <branch> <url>
> wget <url>/refs/head/<branch> ## dump to <myrepo>/refs/head/<branch>
instead of setting $GIT_DIR/remotes/origin file and using "git fetch".
BTW. "git fetch" will not update branch you are on, unless --update-head-ok
option is used.
> git --git-dir <myrepo> read-tree <committish>
>
> cd <srcdir>
> git --git-dir <myrepo> checkout-index -a -f
instead of
git --git-dir=<myrepo> checkout <branch>
(-f is Force a re-read of everything)
> * As far as I can see, there is no reason to have only one index in a
> git repository. Why isn't it possible to specify an alternate
> index-file with an option similar to --git-dir ?
--git-dir is alternative to setting GIT_DIR. You can use GIT_INDEX_FILE
to specify alternate index file. Documented in git(7), section
"ENVIRONMENT VARIABLES".
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-24 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 1:33 updating only changed files source directory? Han-Wen Nienhuys
2006-10-24 5:55 ` Shawn Pearce
2006-10-24 7:48 ` Jakub Narebski [this message]
2006-10-24 9:50 ` Han-Wen Nienhuys
2006-10-24 10:13 ` Jakub Narebski
2006-10-24 19:12 ` Daniel Barkalow
2006-10-25 11:58 ` Han-Wen Nienhuys
2006-10-25 19:35 ` Daniel Barkalow
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='ehkgfs$af6$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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).