From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Hrvoje Nikšić" <hniksic@gmail.com>, git@vger.kernel.org
Subject: Re: 'git add' option to non-interactively stage working tree changes
Date: Fri, 07 Jan 2011 15:50:38 -0800 (PST) [thread overview]
Message-ID: <m3pqs8b7fj.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vfwt45tqv.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> I think it might be Ok to introduce a --full-tree option to "git add" (and
> "git grep"), though. But introduction of corresponding configuration
> variable to flip the default needs to be done carefully in steps across
> major version boundaries as usual (i.e. first introduce --no-full-tree,
You meant --relative[1] here (instead of --no-full-tree), didn't you?
[1] Supported by diff, and in a way by git-diff-tree
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2011-01-07 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 18:56 'git add' option to non-interactively stage working tree changes Hrvoje Nikšić
2011-01-07 19:52 ` Andreas Schwab
2011-01-07 20:03 ` Hrvoje Nikšić
2011-01-07 20:44 ` Junio C Hamano
2011-01-07 23:50 ` Jakub Narebski [this message]
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=m3pqs8b7fj.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hniksic@gmail.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.