git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Dirk Süsserott" <newsletter@dirk.my1.cc>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to "git add ." when some files are not accessible (permission denied)?
Date: Sat, 1 Mar 2008 20:19:00 -0500	[thread overview]
Message-ID: <20080302011900.GC22843@coredump.intra.peff.net> (raw)
In-Reply-To: <47C95E34.1050306@dirk.my1.cc>

On Sat, Mar 01, 2008 at 02:46:28PM +0100, Dirk Süsserott wrote:

> The question is: is there a way to tell "git add ." to add all files but
> ignore those that cannot be added due to lack of authorization?

No, there isn't. Under Linux, I would come up with a list of files I was
interested in and then pipe it to "xargs git-add", which is probably
unhelpful for Windows.

But I think more fundamentally, you probably _do_ want to come up with a
list of files that you can't access and add them to your .gitignore (or
your .git/info/exclude file if they are purely a local matter). That is
the official way to tell all git commands "I really don't care about
these files".  Otherwise they will keep getting brought up when you do,
e.g., a git-status.

> Or, more generally spoken: can I tell "git add" to add only those files  
> it can handle and ignore the rest? The "-f" switch doesn't work and some
> exclude lists on a per file basis are not applicable for my purpose as I
> don't know the files in advance.

The only reason I can think of to not want to generate such an ignore
list is if you are frequently and automagically doing a "git add ." to
pick up new files. For that reason, a "try to continue even if we can't
look at some files" option to git add might make some sense.

-Peff

  reply	other threads:[~2008-03-02  1:19 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 [this message]
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
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=20080302011900.GC22843@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --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 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).