git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Darek Bridges <darek.bridges@me.com>, git@vger.kernel.org
Subject: Re: git with large files...
Date: Fri, 20 Jul 2012 19:28:50 -0400	[thread overview]
Message-ID: <CACPiFC+a=46n-igTUBSDdpgDQyL4cz5vrcpurNBSsb+D1c0UnA@mail.gmail.com> (raw)
In-Reply-To: <86fw8mf3gp.fsf@red.stonehenge.com>

On Fri, Jul 20, 2012 at 6:54 PM, Randal L. Schwartz
<merlyn@stonehenge.com> wrote:
>>>>>> "Darek" == Darek Bridges <darek.bridges@me.com> writes:
>
> Darek> I use git for many things, but I am trying to work out the
> Darek> workflow to use git for deployment.
>
> Don't.

Heh. Best to keep in mind that it just doesn't work very well.
git-bigfiles, git-annex might help you, but look at the docs and
caveats carefully.

Perhaps use rsync, unison work better for you.



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- Software Architect - OLPC
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff

  reply	other threads:[~2012-07-20 23:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 16:27 git with large files Darek Bridges
2012-07-20 22:54 ` Randal L. Schwartz
2012-07-20 23:28   ` Martin Langhoff [this message]
2012-07-21  3:47     ` David Aguilar
2012-07-21  7:11       ` Elia Pinto
2012-07-21 14:42         ` Martin Langhoff
2012-07-21 15:53           ` Elia Pinto
2012-07-22  6:48             ` Elia Pinto
2012-07-22  9:37               ` Kalle Launiala
2012-07-21 21:04           ` Nick
2012-07-21 14:40       ` Martin Langhoff
2012-07-22 20:54   ` Junio C Hamano
2012-07-23  4:23     ` Sitaram Chamarty
2012-07-23  7:23       ` Kalle Launiala
2012-07-29 18:47       ` Drew Northup

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACPiFC+a=46n-igTUBSDdpgDQyL4cz5vrcpurNBSsb+D1c0UnA@mail.gmail.com' \
    --to=martin.langhoff@gmail.com \
    --cc=darek.bridges@me.com \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).