git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
To: git@vger.kernel.org
Subject: Re: way to automatically add untracked files?
Date: Sun, 05 Aug 2007 16:34:58 +0900	[thread overview]
Message-ID: <87hcnejuxp.fsf@catnip.gol.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708042157150.5037@woody.linux-foundation.org> (Linus Torvalds's message of "Sat\, 4 Aug 2007 22\:03\:03 -0700 \(PDT\)")

Linus Torvalds <torvalds@linux-foundation.org> writes:
> But git certainly has the capability. "git commit -a" will notice all the 
> files that went away and automatically remove them, so
>
> 	git add .
> 	git commit -a
>
> will do what you want (except, as we found out last week, we've had a huge 
> performance regression, so that's actually a really slow way to do it, and 
> so it's actually faster to do
>
> 	git ls-files -o | git update-index --add --stdin
> 	git commit -a

I notice that "git ls-files -o" doesn't do normal ignore-processing, so
for instance all my .o and editor backup files show up in the output...
Is that expected or is it a bug (I tried versions "1.5.2.4" and
"1.5.3.rc3.91.g5c75-dirty")?

If I do:

   git-ls-files -o --exclude-per-directory=.gitignore --exclude-from=$HOME/.gitignore

it works more like I'd expect.

Thanks,

-Miles

-- 
`The suburb is an obsolete and contradictory form of human settlement'

  parent reply	other threads:[~2007-08-05  7:34 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  3:31 way to automatically add untracked files? Miles Bader
2007-08-05  3:58 ` Shawn O. Pearce
2007-08-05  4:13   ` Junio C Hamano
2007-08-05  4:00 ` Miles Bader
2007-08-05  4:13   ` Shawn O. Pearce
2007-08-05  4:22     ` Miles Bader
2007-08-05  4:23       ` Junio C Hamano
2007-08-05  4:30         ` Miles Bader
2007-08-05  4:39           ` Junio C Hamano
2007-08-05  4:53             ` Miles Bader
2007-08-05  5:04               ` Junio C Hamano
2007-08-05  5:17                 ` Miles Bader
2007-08-05  5:23                   ` Johannes Schindelin
2007-08-05  5:27                     ` Miles Bader
2007-08-05 11:22             ` Steffen Prohaska
2007-08-05 12:11     ` Johan Herland
2007-08-05 12:17       ` David Kastrup
2007-08-05 16:11       ` Theodore Tso
2007-08-05 19:16         ` Johan Herland
2007-08-06  0:00           ` Miles Bader
2007-08-06  0:16           ` Johannes Schindelin
2007-08-06  3:09             ` Miles Bader
2007-08-06  3:21               ` Johannes Schindelin
2007-08-06  3:45                 ` Miles Bader
2007-08-06  7:46                 ` Johan Herland
2007-08-06 12:17                   ` Johannes Schindelin
2007-08-05 20:04         ` Steffen Prohaska
2007-08-06  0:17           ` Johannes Schindelin
2007-08-06  4:58             ` Steffen Prohaska
2007-08-06  0:32       ` Jakub Narebski
2007-08-06  7:30         ` Johan Herland
2007-08-06  8:45     ` Junio C Hamano
2007-08-06 18:19       ` David Kastrup
2007-08-07  0:08         ` Miles Bader
2007-08-05  5:03   ` Linus Torvalds
2007-08-05  5:14     ` Junio C Hamano
2007-08-05  7:32       ` David Kastrup
2007-08-05 10:33         ` Benchmarking git-add vs git-ls-files+update-index (was: way to automatically add untracked files?) David Kastrup
2007-08-05  7:34     ` Miles Bader [this message]
2007-08-05 17:04       ` way to automatically add untracked files? 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=87hcnejuxp.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --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 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).