From: "Giuseppe Bilotta" <giuseppe.bilotta@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "David Lang" <david@lang.hm>,
"Junio C Hamano" <gitster@pobox.com>,
"Jean-Luc Herren" <jlh@gmx.ch>,
git@vger.kernel.org
Subject: Re: [RFC] Zit: the git-based single file content tracker
Date: Sat, 25 Oct 2008 09:48:24 +0200 [thread overview]
Message-ID: <cb7bb73a0810250048q7ad8595bt565de05ec2ec37cb@mail.gmail.com> (raw)
In-Reply-To: <200810242230.49238.jnareb@gmail.com>
On Fri, Oct 24, 2008 at 10:30 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> Well, with all zit repositories in '.zit/' directory (similar to RCS/)
> you could have point core.excludesfile to _common_ '.zit/excludes';
> the pattern doesn't change from zit repository to zit repository?
>
> You could even use per-user ~/.zitignore (I'm not sure if git expands
> '~' in paths; there was some patch for it, but was it accepted?) or
> system-wide /usr/lib/zitignore or /usr/libexec/zitignore file.
System-wide means maximum space save, but it require system
administration to install Zit, and considering that one of the things
I love of Zit now is its being self contained, I would rather not
depend on anything system-wide anyway.
The user .zitignore file is probably the best approach: we can create
it ourselves (usually), and even if Git doesn't expand the pathname
itself, we can just use an absolute path. I'll go that way.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2008-10-25 7:53 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
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 [this message]
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=cb7bb73a0810250048q7ad8595bt565de05ec2ec37cb@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jlh@gmx.ch \
--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.
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).