git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 'git add' option to non-interactively stage working tree changes

From
Jakub Narebski <jnareb@gmail.com>
Date
Jan 7, 2011, 23:50 UTC
Message-ID
<m3pqs8b7fj.fsf@localhost.localdomain>
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
Previous: Junio C Hamano
Message 5 of 5 in “'git add' option to non-interactively stage working tree changes”
  1. Hrvoje NikšićJan 7, 2011
  2. Andreas SchwabJan 7, 2011
  3. Hrvoje NikšićJan 7, 2011
  4. Junio C HamanoJan 7, 2011
  5. Jakub NarebskiJan 7, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.