git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] per-user ignore file
Date: Mon, 30 Jul 2007 22:41:43 +0200	[thread overview]
Message-ID: <20070730204143.GA8209@efreet.light.src> (raw)
In-Reply-To: <Pine.LNX.4.64.0707301612160.8054@iabervon.org>

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

On Mon, Jul 30, 2007 at 16:28:13 -0400, Daniel Barkalow wrote:
> It would be nice to have a per-user ignore file, so that emacs users can 
> ignore "*~", "#*#", and ".#*". Probably this should be in the form of 
> having a config option for additional ignore file names, so that the user 
> can decide where to put it. (E.g., ~/.gitignore would be an issue if the 
> user is tracking their home directory with git and wants to ignore some 
> files in the home directory repository but track similarly named files in 
> some other repository). Are there any fundamental issues with this, or is 
> it just that nobody's been sufficiently motivated to do it?

I believe the later. Though I also believe it would be useful.

An alternative to separate file would be to include it into .gitconfig
as multi-valued key. Something like:

[core]
ignore = *~
ignore = #*#
ignore = .#*
ignore = .*.sw[nop]

and so on. Could be reused in .git/config as replacement for
.git/info/exclude if desired.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2007-07-30 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 20:28 [RFC] per-user ignore file Daniel Barkalow
2007-07-30 20:36 ` J. Bruce Fields
2007-07-30 20:43   ` Daniel Barkalow
2007-07-30 20:41 ` Jan Hudec [this message]

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=20070730204143.GA8209@efreet.light.src \
    --to=bulb@ucw.cz \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    /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).