From: Pau Garcia i Quiles <pgquiles@elpauer.org>
To: Charles Earl <charles.cearl@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Appropriateness of git for digital video production versioning
Date: Thu, 29 Jan 2009 16:48:35 +0100 [thread overview]
Message-ID: <3af572ac0901290748g5c5b3043j425adbda8f5d7619@mail.gmail.com> (raw)
In-Reply-To: <8c4a72800901290736p4952e53byddca243f300dd8af@mail.gmail.com>
Hello,
Git is not the appropriate tool. What about using a filesystem with
versioning support? tux3, btrfs, ZFS and NILFS may work for you.
On Thu, Jan 29, 2009 at 4:36 PM, Charles Earl <charles.cearl@gmail.com> wrote:
> Hi,
> Are there past instances of git having been adapted to support version
> control of digital media production workflow?
> I'm evaluating CMS and versioning systems for the backend of a SaaS
> for digital media production workflow.
> The bulk of content stored is binary data -- there have been posts on
> this about integration of various binary diff implemetations with git.
> The versioning of metadata, scripts, project structure seems to argue
> for applicability of system such as git -- these fit the paradigm of
> traditional scm.
> Example content is from media production suites such as Adobe After
> Effects/Premier: video, compositions, etc.
> I'd also like the object storage to be in S3/Amazon BlockStore or
> similar remote stores.
> Charles
> --
> 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
>
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
next prev parent reply other threads:[~2009-01-29 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 15:36 Appropriateness of git for digital video production versioning Charles Earl
2009-01-29 15:45 ` Shawn O. Pearce
2009-01-29 15:48 ` Pau Garcia i Quiles [this message]
2009-01-30 10:13 ` Christian MICHON
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=3af572ac0901290748g5c5b3043j425adbda8f5d7619@mail.gmail.com \
--to=pgquiles@elpauer.org \
--cc=charles.cearl@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).