From: Jamie Wellnitz <jwellnitz@gmail.com>
To: Richard Assal <richard_assal@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: git equivalent to clearcase wink-in
Date: Wed, 20 Jan 2010 16:05:46 -0500 [thread overview]
Message-ID: <7938b46a1001201305j499e05bg2654d634d7b26d76@mail.gmail.com> (raw)
In-Reply-To: <810256.84037.qm@web45111.mail.sp1.yahoo.com>
Would something like ccache (compiler cache) help you out? It's not
the same as wink-in (which, as I understand it, copies an already
built object file from someone else who has built it). Instead each
user has their own cache, so everyone has to pay the expensive build
price at least once.
It also only works for C/C++, I think.
-- Jamie
On Wed, Jan 20, 2010 at 3:20 PM, Richard Assal <richard_assal@yahoo.com> wrote:
> To whom it may concer,
>
> I have been playing with git recently, and I like it very much. I was wondering if you can tell me if git has something that is equivalent to clearcase wink-in functionality. The reason I ask, if it takes 1 hour to build my repository, then every clone of my repository will also take one hour to build at the remote location. In clearcase you can wink in objects that have already been built. time to wink in could just be minutes rather than waiting a full hour for all the binaries to build.
>
> Can you help me out here? I would like to know if git has something similar.
>
> Richard.
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-01-20 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:20 git equivalent to clearcase wink-in Richard Assal
2010-01-20 21:05 ` Jamie Wellnitz [this message]
2010-01-20 21:12 ` Mike Hommey
2010-01-20 22:34 ` Sverre Rabbelier
2010-01-21 1:51 ` Johan Herland
2010-01-21 7:46 ` Matthieu Moy
2010-01-20 21:24 ` Robin Rosenberg
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=7938b46a1001201305j499e05bg2654d634d7b26d76@mail.gmail.com \
--to=jwellnitz@gmail.com \
--cc=git@vger.kernel.org \
--cc=richard_assal@yahoo.com \
/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).