Re: [RFC] Zit: the git-based single file content tracker

From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date: Oct 23, 2008, 13:33 UTC
Message-ID: <cb7bb73a0810230633r9970a50mbb4ecf3a855c3a21@mail.gmail.com>
In-Reply-To: <fcaeb9bf0810230550t54813c09m3b1984f065732c0@mail.gmail.com>

On Thu, Oct 23, 2008 at 2:50 PM, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:

Show 11 quoted lines

> On 10/23/08, Giuseppe Bilotta <giuseppe.bilotta@gmail.com> wrote:
>>  The principle is extremely simple: when you choose to start tracking a
>>  file with Zit,
>>
>>  zit track file
>>
>>  Zit will create a directory .zit.file to hold a git repository
>>  tracking the single file .zit.file/file, which is just a hard link to
>>  file.
>
> Why not use one .zit repo and track each file on each own branch?.

So your proposal is to have a single .zit repo which is actually a git repo and where each additional tracked file becomes its own branch, and zit would take care of switching from branch to branch when zit commands are called?

I think this solution would have a number of problems, apart from being generally quite messy. First of all, moving a file and its history somewhere else means toying around with the history of a much wider repo, whereas the current approach would mean just moving the .zit.file dir together with the file (modulo hardlinks). Non-linear histories for a single file would be more complex to handle, too. And publishing just the history of one file would be damn complex.

-- 
Giuseppe "Oblomov" Bilotta