git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Appropriateness of git for digital video production versioning

From
PQPau Garcia i Quiles <pgquiles@elpauer.org>
Date
Jan 29, 2009, 15:48 UTC
Message-ID
<3af572ac0901290748g5c5b3043j425adbda8f5d7619@mail.gmail.com>
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:
Show 20 quoted lines
> 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)
Previous: Shawn O. PearceNext: Christian MICHON
Message 3 of 4 in “Appropriateness of git for digital video production versioning”
  1. Charles EarlJan 29, 2009
  2. Shawn O. PearceJan 29, 2009
  3. Pau Garcia i QuilesJan 29, 2009
  4. Christian MICHONJan 30, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.