git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: updating only changed files source directory?
Date: Wed, 25 Oct 2006 13:58:50 +0200	[thread overview]
Message-ID: <453F517A.7060000@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0610241435420.9789@iabervon.org>

Daniel Barkalow escreveu:
>> I'm just starting out with GIT.  Initially, I want to use experiment with
>> integrating it into our binary builder structure for LilyPond.
>>
>> The binary builder roughly does this:
>>
>>  1. get source code updates from a server to a single, local
>>     repository. This is currently a git repository that is that
>>     tracks our CVS server.
>>
>>  2. copy latest commit from a branch to separate source directory.
>>     This copy should only update files that changed.
>>
>>  3. Incrementally compile from that source directory
> 
> The terminology in the git world is, I think, a little different from what 
> you expect. We call the thing that contains all of the tracked information 
> (what you're calling the repository) the "object database"; what we call 

yes, you hit the nail on the head.

> referencing an external one. So you need a repository for each source 
> directory (because it keeps track of what commit is currently in the 
> source directory), but it doesn't need to have its own complete object 
> database, which is what you're trying to share between all of them.

OK. This makes sense; thanks for this pointer.

How can I set the object database?  I found GIT_OBJECT_DIRECTORY, but 
can I write a config file entry for that?

> built it in that directory. You fetch into the single bare repository 
> from upstream, and then pull into each source directory from the bare 
> repository; this will do the minimal update to the contents of the source 
> directory automatically.

yes, this works. Thanks!

-- 

  reply	other threads:[~2006-10-25 11:58 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
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 [this message]
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=453F517A.7060000@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=barkalow@iabervon.org \
    --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).