From: fork0@t-online.de (Alex Riesen)
To: Junio C Hamano <junkio@cox.net>
Cc: Martin Waitz <tali@admingilde.org>, git@vger.kernel.org
Subject: Re: git refuses to switch to older branches
Date: Sun, 20 Aug 2006 09:26:12 +0200 [thread overview]
Message-ID: <20060820072612.GA6003@steel.home> (raw)
In-Reply-To: <7vac601hbb.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano, Sun, Aug 20, 2006 00:39:20 +0200:
> Martin Waitz <tali@admingilde.org> writes:
>
> > This safety measure is quite useful normally, but for files that are
> > explicitly marked as to-be-ignored it should not be neccessary.
> >
> > But all the code that handles .gitignore is only used by ls-files now.
> > Does it make sense to add exclude handling to unpack-trees.c, too?
>
> In principle, I am not opposed to the idea of making read-tree
> take the ignore information into consideration.
>
> But I would suggest you to be _extremely_ careful if you want to
It should be optional. And off by default, people already have got
scripts depending on this behaviour (well, I have).
> try this. I do not have an example offhand, but I would not be
> surprised at all if there is a valid use case where it is useful
> to have a pattern that matches a tracked file in .gitignore
> file.
>
Ignored directory and but some files/subdirectories in it are tracked,
because this is temporary or externally changed data (I have both
examples).
next prev parent reply other threads:[~2006-08-20 7:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-19 20:25 git refuses to switch to older branches Martin Waitz
2006-08-19 21:47 ` Jakub Narebski
2006-08-19 22:41 ` Junio C Hamano
2006-08-19 22:48 ` Jakub Narebski
2006-08-20 1:34 ` Junio C Hamano
2006-08-19 22:39 ` Junio C Hamano
2006-08-19 22:44 ` Petr Baudis
2006-08-20 12:21 ` Martin Waitz
2006-08-20 12:48 ` Johannes Schindelin
2006-08-20 18:15 ` Martin Waitz
2006-08-20 18:46 ` Johannes Schindelin
2006-08-20 19:11 ` Josef Weidendorfer
2006-08-20 7:26 ` Alex Riesen [this message]
2006-08-20 12:19 ` Martin Waitz
2006-09-08 22:00 ` Alex Riesen
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=20060820072612.GA6003@steel.home \
--to=fork0@t-online.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@gmail.com \
--cc=tali@admingilde.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).