Thread (1 message) 1 message, 1 author, 2019-11-13

Re: Change behavior of git add --patch on newly added file?

From: Junio C Hamano <hidden>
Date: 2019-11-13 01:47:47

Emily Shaffer [off-list ref] writes:
quoted
Patches welcome, but you may want to check with Dscho as there is an
effort going on to reimplement the entire "add -i" machinery in C.
Ah, this is a compelling point. I imagine the landscape will be fairly
different when that effort is finished.


From the replies, it sounds like it's a favorable change, but it makes
sense to wait on it considering the refactor to use C. Thanks, all.
Peff's "how would you tell between genuinely untracked ones and
those you would want to add" and "should 'add -p' with no pathspec
attempt to 'add -N' everything under the sun?" are both quite valid
points.  I already raised "'add -N && add -p' would give you a
single hunk that adds everything. Are you willing to manually split,
and how well would it work?" in a separate message.  These design
issues can be resolved without coding, and should be resolved before
you start randomly typing ;-)

Thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help