From: Mark Burton <markb@ordern.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Git commit won't add an untracked file given on the command line
Date: Wed, 19 Nov 2008 23:30:27 +0000 [thread overview]
Message-ID: <20081119233027.17687dd5@crow> (raw)
In-Reply-To: <7v7i6zs4ay.fsf@gitster.siamese.dyndns.org>
Hi,
> Allowing what Mark wants without any explicit user customization will be a
> disaster to the end user experience.
If the ability to commit a currently untracked file/tree whilst
preserving the index is really worth having (and that's debatable, as
the git user community has survived until now without that capability)
then another option (say, -O) could be added to git-commit that does
what -o does but allows untracked files/trees to be specified - that
way, the current behaviour would remain unchanged and the above
mentioned disaster averted.
Cheers,
Mark
next prev parent reply other threads:[~2008-11-19 23:32 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
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 [this message]
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=20081119233027.17687dd5@crow \
--to=markb@ordern.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.