From: Pavel Roskin <proski@gnu.org>
To: Sean <seanlkml@sympatico.ca>
Cc: jnareb@gmail.com, git@vger.kernel.org
Subject: Re: "git add $ignored_file" fail
Date: Wed, 17 May 2006 15:56:56 -0400 [thread overview]
Message-ID: <1147895816.30618.6.camel@dv> (raw)
In-Reply-To: <20060517153903.6b896fdd.seanlkml@sympatico.ca>
On Wed, 2006-05-17 at 15:39 -0400, Sean wrote:
> On Wed, 17 May 2006 15:23:06 -0400
> Pavel Roskin <proski@gnu.org> wrote:
>
> Shouldn't git just always respect the ignore rules? Forcing someone to
> remove a file from the .gitignore or employ the other work around
> mentioned earlier doesn't seem too bad. How often are people adding
> files that are explicitly ignored?
That's a good idea! And the implementation should be easy - if the file
is present, but git-ls-file doesn't show it, tell the user to
adjust .gitignore or to use some flag like --force.
Libification of git-ls-files would allow even more precise messages.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-05-17 19:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 22:07 "git add $ignored_file" fail Santi
2006-05-16 22:28 ` Linus Torvalds
2006-05-16 22:41 ` Jakub Narebski
2006-05-16 22:42 ` Santi
2006-05-17 11:08 ` Johannes Schindelin
[not found] ` <81b0412b0605170604i689a8f7axa5aeb7752dc72072@mail.gmail.com>
2006-05-17 13:41 ` Santi
2006-05-17 13:46 ` Jakub Narebski
2006-05-17 19:23 ` Pavel Roskin
[not found] ` <20060517153903.6b896fdd.seanlkml@sympatico.ca>
2006-05-17 19:39 ` Sean
2006-05-17 19:52 ` Jakub Narebski
2006-05-17 19:56 ` Pavel Roskin [this message]
2006-05-17 20:26 ` Linus Torvalds
2006-05-17 20:35 ` Jakub Narebski
2006-05-17 20:53 ` Linus Torvalds
2006-05-17 23:07 ` Junio C Hamano
2006-05-17 23:20 ` Linus Torvalds
2006-05-17 13:48 ` Johannes Schindelin
2006-05-17 14:49 ` Linus Torvalds
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=1147895816.30618.6.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=seanlkml@sympatico.ca \
/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).