Sorry, I just realized that when the hunks are across file boundaries, it won't go back to it. I think this is a bit misleading, it would be great to see it go back to the ACTUAL previous hunk, regardless of which file it came from.
On Thu, Sep 4, 2014 at 4:54 PM, Robert Dailey <[email protected]> wrote: > I run the following: > > $ git add -p > > I skip the first hunk by typing "n". At the next hunk, I try "k" and > "K". In both cases, it shows me the same hunk I'm on again and says > "No previous hunk". > > Is this intended behavior? I expect to be taken back to the previous > hunk that I did not stage. > > Running Git 2.1.0 on msysgit Windows. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
