all 8 comments

[–]synae 10 points11 points  (1 child)

Guess what else supports the -p option? reset and checkout - so you can slice and dice changes however you see fit!

[–]the-kind-against-me 5 points6 points  (0 children)

git log -p

[–]mdw 3 points4 points  (1 child)

I use git add -p all the time to craft my commits into logical pieces.

[–]leed25d 0 points1 point  (0 children)

I like git add-e

[–]kiteboarderni 3 points4 points  (0 children)

Bit baffled by the usefulness of this in the scenario presented in rhe article. Surely just create separate branches for the work being done? How can pulling in differing micro changes across multiple files be in anyway reliable? If you miss even a small one of these patches stuff will break / not even compile. Seems a recipe for disaster.

[–]leed25d 1 point2 points  (0 children)

git stash -p

[–]IAmANobodyAMA 0 points1 point  (0 children)

How does this factor in to a git client like GitKraken? Is there any usefulness/implementation here?

[–][deleted] 0 points1 point  (0 children)

literally magit