From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] git add: notice removal of tracked paths by default
Date: Tue, 19 Apr 2011 23:47:06 +0200 [thread overview]
Message-ID: <BANLkTimKL2bbmOdh35FDZwf2uAzO=nJkFQ@mail.gmail.com> (raw)
In-Reply-To: <7voc41537g.fsf@alter.siamese.dyndns.org>
Heya,
On Tue, Apr 19, 2011 at 23:41, Junio C Hamano <gitster@pobox.com> wrote:
> But as I said, I do not have a strong opinion for this change, other than
> "if we need this optional, then it is not worth doing this".
Your argument makes sense, and I personally haven't run into a case
where I _wouldn't_ want the suggested behavior, and I have run into
cases several times where I _would've_ wanted the suggested behavior.
So consider this a +1 for me on the idea.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2011-04-19 21:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 19:18 [RFC/PATCH] git add: notice removal of tracked paths by default Junio C Hamano
2011-04-19 19:46 ` Sverre Rabbelier
2011-04-19 21:41 ` Junio C Hamano
2011-04-19 21:47 ` Sverre Rabbelier [this message]
2011-04-20 5:57 ` Jeff King
2011-04-20 8:18 ` Michael J Gruber
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='BANLkTimKL2bbmOdh35FDZwf2uAzO=nJkFQ@mail.gmail.com' \
--to=srabbelier@gmail.com \
--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 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).