From: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>
To: "Jean-Luc Herren" <jlh@gmx.ch>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Zit: the git-based single file content tracker
Date: Fri, 24 Oct 2008 08:55:55 +0200 [thread overview]
Message-ID: <cb7bb73a0810232355u6de0479cyc260c80227f44e59@mail.gmail.com> (raw)
In-Reply-To: <4901077A.7050904@gmx.ch>
On Fri, Oct 24, 2008 at 1:23 AM, Jean-Luc Herren <jlh@gmx.ch> wrote:
> Hi!
>
> Giuseppe Bilotta wrote:
>> So today I decided to start hacking at a git-based but file-oriented
>> content tracker, which I decided to name Zit.
>
> This sounds great and would seem very useful to manage my ~/bin/
> directory which contains a set of unrelated one-file-tools that
> evolve over time. I haven't played with it yet though.
Nice to see I wasn't the only one with such a need 8-)
>> when you choose to start tracking a file with Zit [...]
>> Zit will create a directory .zit.file to hold a git repository
>
> If you have many files you want to track in a single directory
> (like ~/bin/), all those additional directories will quickly feel
> like clutter. If you track every file, it will even double the
> number of things you see with an "ls -a".
Ah, good point, I hadn't thought about that.
> If you decide against a shared repository, maybe you want to
> consider to not use ".zit.file/", but ".zit/file/" as the
> repository? This would reduce the clutter to a single directory,
> just like with ".git". And moving files around wouldn't be that
> much complicated.
Right. I'll give that a shot.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2008-10-24 6:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 1:29 [RFC] Zit: the git-based single file content tracker Giuseppe Bilotta
2008-10-23 12:33 ` Felipe Oliveira Carvalho
2008-10-23 12:50 ` Nguyen Thai Ngoc Duy
2008-10-23 13:33 ` Giuseppe Bilotta
2008-10-23 13:51 ` Nguyen Thai Ngoc Duy
2008-10-23 14:21 ` Giuseppe Bilotta
2008-10-23 13:03 ` Johannes Sixt
2008-10-23 13:28 ` Giuseppe Bilotta
2008-10-24 17:44 ` Johannes Schindelin
2008-10-24 17:48 ` Giuseppe Bilotta
2008-10-23 17:22 ` [RFC] Zit (v2): " Giuseppe Bilotta
2008-10-24 6:21 ` david
2008-10-24 7:14 ` Giuseppe Bilotta
2008-10-24 10:43 ` Jakub Narebski
2008-10-24 11:01 ` Giuseppe Bilotta
2008-10-26 15:20 ` Jakub Narebski
2008-10-26 21:18 ` Giuseppe Bilotta
2008-10-26 22:04 ` Jakub Narebski
2008-10-26 22:16 ` Giuseppe Bilotta
2008-10-23 23:23 ` [RFC] Zit: " Jean-Luc Herren
2008-10-24 6:55 ` Giuseppe Bilotta [this message]
2008-10-24 10:31 ` Jakub Narebski
2008-10-24 10:52 ` Giuseppe Bilotta
2008-10-24 11:32 ` Jakub Narebski
2008-10-24 12:15 ` Giuseppe Bilotta
2008-10-24 18:28 ` Junio C Hamano
2008-10-24 19:11 ` david
2008-10-24 19:42 ` Giuseppe Bilotta
2008-10-24 19:46 ` david
2008-10-24 19:51 ` Giuseppe Bilotta
2008-10-24 19:54 ` david
2008-10-24 20:13 ` Giuseppe Bilotta
2008-10-24 20:30 ` Jakub Narebski
2008-10-25 7:48 ` Giuseppe Bilotta
2008-10-25 9:10 ` Jakub Narebski
2008-10-25 10:30 ` Giuseppe Bilotta
2008-10-24 19:53 ` david
2008-10-24 20:06 ` Giuseppe Bilotta
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=cb7bb73a0810232355u6de0479cyc260c80227f44e59@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=git@vger.kernel.org \
--cc=jlh@gmx.ch \
/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).