From: Miles Bader <miles@gnu.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Mark Burton <markb@ordern.com>,
Francis Galiegue <fge@one2team.com>,
git@vger.kernel.org
Subject: Re: Git commit won't add an untracked file given on the command line
Date: Wed, 19 Nov 2008 10:21:19 +0900 [thread overview]
Message-ID: <87tza41pf4.fsf@catnip.gol.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0811190206170.30769@pacific.mpi-cbg.de> (Johannes Schindelin's message of "Wed, 19 Nov 2008 02:07:41 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> It may be a traditional wart, but a helpful one. Remember, you can also
> say:
>
> git commit that/directory/
>
> I do _not_ want Git to add all untracked (and unignored) files in that
> directory automatically.
I agree, but it would kinda handy to have an exception for files
explicitly named on the command line.
-Miles
--
Apologize, v. To lay the foundation for a future offense.
next prev parent reply other threads:[~2008-11-19 1:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 21:12 Git commit won't add an untracked file given on the command line Mark Burton
2008-11-18 21:27 ` Francis Galiegue
2008-11-18 21:47 ` Mark Burton
2008-11-19 1:07 ` Johannes Schindelin
2008-11-19 1:21 ` Miles Bader [this message]
2008-11-19 1:39 ` Johannes Schindelin
2008-11-19 3:43 ` Miles Bader
2008-11-19 9:41 ` Johannes Schindelin
2008-11-20 5:06 ` Miles Bader
2008-11-19 1:51 ` Junio C Hamano
2008-11-19 9:54 ` Mark Burton
2008-11-19 11:27 ` Johannes Schindelin
2008-11-19 13:22 ` Junio C Hamano
2008-11-19 14:41 ` Mark Burton
2008-11-19 18:01 ` Daniel Barkalow
2008-11-19 23:07 ` Junio C Hamano
2008-11-19 23:30 ` Mark Burton
2008-11-19 23:51 ` Junio C Hamano
2008-11-19 23:52 ` Daniel Barkalow
2008-11-20 0:36 ` Junio C Hamano
2008-11-20 10:18 ` David Aguilar
2008-11-18 22:16 ` Matthieu Moy
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=87tza41pf4.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=fge@one2team.com \
--cc=git@vger.kernel.org \
--cc=markb@ordern.com \
/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.