All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Hengeveld <nickh@reactrix.com>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: binary safe?
Date: Thu, 3 Nov 2005 15:05:21 -0800	[thread overview]
Message-ID: <20051103230521.GA3001@reactrix.com> (raw)
In-Reply-To: <86br115r0z.fsf@blue.stonehenge.com>

On Thu, Nov 03, 2005 at 02:02:20PM -0800, Randal L. Schwartz wrote:

> What problems, if any, will I have using git to manage the binary
> files for my site, like the custom icons?  CVS is doing that just fine
> now.

We're now using git in production to distribute content, of which well
over 90% is binary files.  Works great.

-- 
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.

      parent reply	other threads:[~2005-11-03 23:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 22:02 binary safe? Randal L. Schwartz
2005-11-03 22:49 ` Junio C Hamano
2005-11-03 23:00   ` Martin Langhoff
2005-11-04 16:54     ` David Brown
2005-11-04 21:22       ` Martin Langhoff
2005-11-04 21:27         ` David Brown
2005-11-03 22:50 ` Linus Torvalds
2005-11-04  3:49   ` Chris Wedgwood
2005-11-03 23:05 ` Nick Hengeveld [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=20051103230521.GA3001@reactrix.com \
    --to=nickh@reactrix.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.