nissshh · November 27, 2017 05:54
diff --git a/GIT Patch Management b/GIT Patch Management
 At times you may be gated to not checking some files due to dependency on reviewer or functiolnality not completely. Simply say , tha you have to share your changes
 and at the same time you cannot chcking. ut you still want to share the change with the team . e.g. change in the bottomose layer like entties and and persistanc layes

 One way is to create a new branch and ask other to switch , but this leads to nested merges later on. I found a simply way is to use a patch

 I used it via Eclispse PATCH Team>Crat PAtch ... . This will ask you to create multiple patch files depending on your project and then thei patch file can be sahted wiuth the team to appy 
 locally. Voilla !! 

 So when thigs are checked in the patch can be removed. This is helpfull when you are mergin and you got issue, You can simply refert the patched files and lonce merge issue areresolved path again.
	At times you may be gated to not checking some files due to dependency on reviewer or functiolnality not completely. Simply say , tha you have to share your changes
	and at the same time you cannot chcking. ut you still want to share the change with the team . e.g. change in the bottomose layer like entties and and persistanc layes

	One way is to create a new branch and ask other to switch , but this leads to nested merges later on. I found a simply way is to use a patch

	I used it via Eclispse PATCH Team>Crat PAtch ... . This will ask you to create multiple patch files depending on your project and then thei patch file can be sahted wiuth the team to appy
	locally. Voilla !!

	So when thigs are checked in the patch can be removed. This is helpfull when you are mergin and you got issue, You can simply refert the patched files and lonce merge issue areresolved path again.