doc: Give more details about generating patches with base commit information.
* doc/contributing.texi (Submitting Patches): Talk more about '--base'.
This commit is contained in:
		
							parent
							
								
									1f5c1bc024
								
							
						
					
					
						commit
						f697fc267c
					
				
					 1 changed files with 5 additions and 2 deletions
				
			
		|  | @ -1017,8 +1017,11 @@ please run through this check list: | ||||||
| @cindex @code{git format-patch} | @cindex @code{git format-patch} | ||||||
| @cindex @code{git-format-patch} | @cindex @code{git-format-patch} | ||||||
| @item | @item | ||||||
| We recommend to use the command @code{git format-patch --base} to | When generating your patches with @code{git format-patch} or @code{git | ||||||
| include the commit where your patch applies. | send-email}, we recommend using the option @code{--base=}, perhaps with | ||||||
|  | the value @code{auto}.  This option adds a note to the patch stating | ||||||
|  | which commit the patch is based on.  This helps reviewers understand how | ||||||
|  | to apply and review your patches. | ||||||
| 
 | 
 | ||||||
| @item | @item | ||||||
| If the authors of the packaged software provide a cryptographic | If the authors of the packaged software provide a cryptographic | ||||||
|  |  | ||||||
		Reference in a new issue