git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: First round of UGFWIINI results
Date: Sat, 28 Mar 2009 03:42:05 -0400	[thread overview]
Message-ID: <20090328074205.GB9013@coredump.intra.peff.net> (raw)
In-Reply-To: <m37i2b2ecu.fsf@localhost.localdomain>

On Fri, Mar 27, 2009 at 08:08:04AM -0700, Jakub Narebski wrote:

> Not exactly UGFWIINI yet, but:
> 
>   "Music collaboration via git?"
>   http://www.37signals.com/svn/posts/1655-music-collaboration-via-git
>   (sharing LilyPond source files for music notation).

I do something similar, though I am usually not writing in lilypond but
rather in ABC or human-readable chord charts with accompanying lyrics.
However, my band-mates are not git-literate, so I usually end up pulling
their versions directly from email into the working tree, and then
committing to git myself.

For added UGFWIINI, I also keep multitrack recording projects in the
same repo. Live single tracks are kept as pristine "source", and then
are mixed down (with filters and effects added) into a final product.
It's even driven by make. ;)

However, the source files are annoyingly large to work with in git, so I
keep them outside of the repo as immutable source and refer to them by
unique name. Only the ways in which they are filtered or combined are in
the repo.

-Peff

  reply	other threads:[~2009-03-28  7:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 16:47 First round of UGFWIINI results Johannes Schindelin
2009-02-17 17:29 ` Sverre Rabbelier
2009-02-17 23:49   ` Johannes Schindelin
2009-02-17 23:51     ` Sverre Rabbelier
2009-02-17 17:39 ` martin f krafft
2009-02-17 18:04   ` Mike Hommey
2009-02-17 23:51   ` Johannes Schindelin
2009-02-17 18:00 ` Michael J Gruber
2009-02-17 18:34 ` Sergio Callegari
2009-02-19 10:32 ` Peter Krefting
2009-03-03 10:30 ` Jakub Narebski
2009-03-03 11:20   ` Johannes Schindelin
2009-03-07  0:56   ` Jakub Narebski
2009-03-07  2:40     ` Johannes Schindelin
2009-03-03 15:09 ` Reece Dunn
2009-03-03 15:59   ` Johannes Schindelin
2009-03-03 16:04     ` Junio C Hamano
2009-03-03 16:26       ` Sverre Rabbelier
2009-03-03 17:36         ` Johannes Schindelin
2009-03-03 17:28       ` Johannes Schindelin
2009-03-03 16:15     ` Jeff King
2009-03-03 17:27       ` Johannes Schindelin
2009-03-03 17:31         ` Reece Dunn
2009-03-03 17:34         ` Jeff King
2009-03-03 17:49           ` Johannes Schindelin
2009-03-11 10:27 ` Jakub Narebski
2009-03-11 12:09   ` Johannes Schindelin
2009-03-27 15:08 ` Jakub Narebski
2009-03-28  7:42   ` Jeff King [this message]
2009-04-22 10:52 ` Pieter de Bie

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=20090328074205.GB9013@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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).