From: Miles Bader <miles.bader@necel.com>
To: git@vger.kernel.org
Subject: Re: way to automatically add untracked files?
Date: Mon, 06 Aug 2007 12:45:19 +0900 [thread overview]
Message-ID: <buovebtwckw.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708060419230.14781@racer.site> (Johannes Schindelin's message of "Mon\, 6 Aug 2007 04\:21\:30 +0100 \(BST\)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> > I recommend against that, too. All too often, I have some temporary files
>> > in the working tree, and I'll be dimmed if I'm the only one. So
>> > "addremove" adds too much possibility for pilot errors.
>>
>> "Recommend against it"? Why?
>
> Didn't I say that? It just _asks_ for pilot errors.
Huh? How is it any worse than the underlying commands it uses
("git add ." in particular)?! Indeed, it seems rather less likely to
cause problems, because it has a rather odd name.
>> It's a separate command, so if it doesn't fit your working style, don't
>> use it.
>
> Hah! If that were true, we'd have a lot less mails like "I tried this and
> it did not work", only to find out that the person assumed that
> documentation is for wimps, and tried a command that "sounded" like it
> would do the right thing.
Git is not exactly a user-coddling, ultra-hand-holding application, nor
does it seem to have that as a goal. It offers _tons_ of rope to hang
yourself if you wish (though it usually offers lots of ways to recover).
Rather git seems to have as a goal being a useful toolkit for managing
source trees, and based on what I've seen, tries to accomodate many
different styles of usage (rather than trying to force a certain style
down the users' throats -- as some VCSs try to do ...).
-miles
--
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.
next prev parent reply other threads:[~2007-08-06 3:45 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 [this message]
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 ` way to automatically add untracked files? Miles Bader
2007-08-05 17:04 ` 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=buovebtwckw.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=git@vger.kernel.org \
--cc=miles@gnu.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).