Johannes Schindelin [off-list ref] writes:
Hi,
On Thu, 15 Feb 2007, Matthieu Moy wrote:
quoted
Is there a way to have a per-user ignore list in git?
It's not really per user, but how about doing it with templates?
Correct me if I'm wrong (I didn't really find a documentation for
templates), but I believe this would only apply to newly created
project. Then, it doesn't apply if I clone the project of someone
using another editor for example, nor to my old projects if I add
something to the list of things I want to ignore.
--
Matthieu
Hi,
[Cc'ed Duy, as he raised the same concerns.]
On Thu, 15 Feb 2007, Matthieu Moy wrote:
Johannes Schindelin [off-list ref] writes:
quoted
On Thu, 15 Feb 2007, Matthieu Moy wrote:
quoted
Is there a way to have a per-user ignore list in git?
It's not really per user, but how about doing it with templates?
Correct me if I'm wrong (I didn't really find a documentation for
templates), but I believe this would only apply to newly created
project.
Yes. However, you can safely call "git init" in an _existing_ repo. It
does not overwrite existing files.
Then, it doesn't apply if I clone the project of someone using another
editor for example, nor to my old projects if I add something to the
list of things I want to ignore.
"git clone" implicitly calls "git init"; Therefore you get the templates,
too. But you're right, if you already edited .git/info/exclude, this will
not overwrite it.
Of course, you could fiddle with ~/.gitconfig, or even ~/.gitignore, but I
suggest that you first think about a sane syntax.
Also note that this opens the door for shooting-in-the-foot; files you are
certain you want ignored can show up in a cloned repo all to easy.
Ciao,
Dscho
On 2/15/07, Johannes Schindelin [off-list ref] wrote:
Yes. However, you can safely call "git init" in an _existing_ repo. It
does not overwrite existing files.
Oh.. that's enough for me :-)
--
Duy