From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: "git add $ignored_file" fail
Date: Wed, 17 May 2006 22:35:55 +0200 [thread overview]
Message-ID: <e4g1f4$anv$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0605171325200.10823@g5.osdl.org
Linus Torvalds wrote:
> On Wed, 17 May 2006, Pavel Roskin wrote:
>> [...] 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.
>
> Umm. That's exactly the semantics for "git add" right now. We _always_
> respect the ignore rules.
>
> That was what people were complaining about.
>
> Although I think Santi realized why we do it, and isn't even complaining
> any more.
>
> So we're all good again.
The changes in docummentation are nice and dandy, but it would be even nicer
if "git add" told us about "git update-index --add" when it adds no files,
as it is certainly the case when something is wrong (perhaps user
expectations, but still...).
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-05-17 20:36 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
2006-05-17 19:39 ` Sean
2006-05-17 19:39 ` Sean
2006-05-17 19:52 ` Jakub Narebski
2006-05-17 19:56 ` Pavel Roskin
2006-05-17 20:26 ` Linus Torvalds
2006-05-17 20:35 ` Jakub Narebski [this message]
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='e4g1f4$anv$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.