From: Matt Porter <mporter@kernel•crashing.org>
To: Junio C Hamano <junkio@cox•net>
Cc: Petr Baudis <pasky@ucw•cz>, git@vger•kernel.org
Subject: Re: [PATCH] Add exclude file support to cg-status
Date: Mon, 2 May 2005 19:33:43 -0700 [thread overview]
Message-ID: <20050502193343.A25462@cox.net> (raw)
In-Reply-To: <7vd5s9nmio.fsf@assigned-by-dhcp.cox.net>; from junkio@cox.net on Mon, May 02, 2005 at 06:09:19PM -0700
On Mon, May 02, 2005 at 06:09:19PM -0700, Junio C Hamano wrote:
> >>>>> "MP" == Matt Porter <mporter@kernel•crashing.org> writes:
>
> MP> Adds a trivial per-repository exclude file implementation for
> MP> cg-status on top of the new git-ls-files option.
>
>
> MP> +EXCLUDEFILE=.git/exclude
>
> Good intentions, but shouldn't the file be .git/info/exclude
> (i.e. under .git/info)?
My reasoning for not doing something like this was that there is
only ever one exclude file. In other instances of cogito specific
data in the .git directory, there is a subdir named for the class
of data being stored there (i.e. branches, refs). In this case,
it didn't seem necessary. On the other hand, this made me
wonder whether there should just be a .git/cginfo subdir where
exclude, branches, refs, etc. all live under since they are
cogito specfic functionality. Something like:
.git/cginfo/
exclude
branches/
refs/
and so on...
-Matt
next prev parent reply other threads:[~2005-05-03 2:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 0:10 [PATCH] Add exclude file support to cg-status Matt Porter
2005-05-03 1:09 ` Junio C Hamano
2005-05-03 2:33 ` Matt Porter [this message]
2005-05-03 4:15 ` Junio C Hamano
2005-05-03 4:21 ` Matt Porter
2005-05-03 4:27 ` Matt Porter
2005-05-08 1:50 ` Petr Baudis
2005-05-08 23:28 ` Junio C Hamano
2005-05-08 23:42 ` Petr Baudis
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=20050502193343.A25462@cox.net \
--to=mporter@kernel$(echo .)crashing.org \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=pasky@ucw$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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