I'm new to git. 

I had posted my question earlier on StackOverflow, here: 

To summarize the problem described in above question: Even a *revert* of a 
commit that I perceived to be "simple enough" (in the middle of a series of 
commits) was failing. Apparently, the underlying reason behind my failed 
*revert* was the "context" that is always used by the *revert* operation.

While I more or less understand that reason now, I have a another related 
question suitable for this group. 

*Question: 1. *Would having a new option (such as *--ignore-patch-context *) 
while doing *git revert* make sense? This option when used would carry out 
the *revert* mechanically/blindly and leave the result in an uncommitted 
state (with maybe a warning on the console), allowing the user to verify 
things for syntax and semantics before committing.  

2. Is there any documentation where such details of the operations (such as 
*revert*, *merge, *...) are described?


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to