All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joachim B Haga <cjhaga@fys.uio.no>
To: git@vger.kernel.org
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Dirk Süsserott" <newsletter@dirk.my1.cc>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] Make the exit code of add_file_to_index actually useful
Date: Sun, 02 Mar 2008 23:04:43 +0100	[thread overview]
Message-ID: <85ablgkcjo.fsf@lupus.strangled.net> (raw)
In-Reply-To: 20080302214241.GB13954@steel.home

Alex Riesen <raa.lkml@gmail.com> writes:

> Junio C Hamano, Sun, Mar 02, 2008 17:59:13 +0100:
>> Why is this even needed to begin with?  I am aware of Dirk's original
>> issue discussed elsewhere, but we try fairly hard to be A-O-N when we can
>> afford to, and this option deliberately breaks it.  What is the real
>> reason why such an unreadable (either for privilege or for I/O error)
>> file should not live in .gitignore?
>
> Another program keeps the file open. There is an exclusive mode for
> opening files, which locks the files for everyone. I believe it is
> even default mode, unless selected otherwise.

Another minor annoyance in this area, is when a wildcard add fails
because of ignored files:

  potassium ~/svn/Deformation|master 0$ ls EpetraMatrix.*
  EpetraMatrix.cpp  EpetraMatrix.cpp~  EpetraMatrix.h  EpetraMatrix.o
  potassium ~/svn/Deformation|master 0$ git add EpetraMatrix.*
  The following paths are ignored by one of your .gitignore files:
  EpetraMatrix.cpp~
  EpetraMatrix.o
  Use -f if you really want to add them.
  potassium ~/svn/New-Deformation|master 0$ git status
  # On branch master
  # Changed but not updated:
  #   (use "git add <file>..." to update what will be committed)
  #
  [...]

I don't want to add them, I just want to ignore them completely (i.e., 
add the un-ignored ones).

Would this case also be covered by the new switch?

-j.


  reply	other threads:[~2008-03-02 22:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01 13:46 How to "git add ." when some files are not accessible (permission denied)? Dirk Süsserott
2008-03-02  1:19 ` Jeff King
2008-03-03 19:17   ` Dirk Süsserott
2008-03-03 20:06     ` Junio C Hamano
2008-03-03 20:32       ` Dirk Süsserott
2008-03-02 15:41 ` Alex Riesen
2008-03-02 15:42   ` [PATCH] Make the exit code of add_file_to_index actually useful Alex Riesen
2008-03-02 15:43     ` [PATCH] Extend interface of add_files_to_cache to allow ignore indexing errors Alex Riesen
2008-03-02 15:44       ` [PATCH] Add --ignore-errors to git-add to allow it to skip files with read errors Alex Riesen
2008-03-02 15:44         ` [PATCH] Add a test for git-add --ignore-errors Alex Riesen
2008-03-02 15:57     ` [PATCH] Make the exit code of add_file_to_index actually useful Johannes Schindelin
2008-03-02 16:59       ` Junio C Hamano
2008-03-02 21:42         ` Alex Riesen
2008-03-02 22:04           ` Joachim B Haga [this message]
2008-03-03  6:57             ` Alex Riesen
2008-05-12 17:56         ` Alex Riesen
2008-05-12 17:57           ` Alex Riesen
2008-05-12 17:58             ` [PATCH] Extend interface of add_files_to_cache to allow ignore indexing errors Alex Riesen
2008-05-12 17:58               ` [PATCH] Add --ignore-errors to git-add to allow it to skip files with read errors Alex Riesen
2008-05-12 17:58                 ` [PATCH] Add a test for git-add --ignore-errors Alex Riesen
2008-05-12 17:59                   ` [PATCH] Add a config option to ignore errors for git-add Alex Riesen
2008-05-13  3:48                   ` [PATCH] Add a test for git-add --ignore-errors Junio C Hamano
2008-05-13  6:04                     ` Alex Riesen
2008-05-13  6:05                     ` Junio C Hamano
2008-05-13 22:28                       ` Alex Riesen
2008-05-12 18:42           ` [PATCH] Make the exit code of add_file_to_index actually useful Junio C Hamano
2008-05-12 20:54             ` Alex Riesen
2008-05-12 22:19               ` Junio C Hamano
2008-05-12 22:48                 ` Alex Riesen
2008-05-12 23:32                   ` Junio C Hamano
2008-05-13  6:00                     ` Alex Riesen
2008-03-03 18:01       ` Daniel Barkalow

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=85ablgkcjo.fsf@lupus.strangled.net \
    --to=cjhaga@fys.uio.no \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=newsletter@dirk.my1.cc \
    /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.