RE: commit sized around 100 gb in changes failed to push to a TFS remote - Git

2019-06-14 Thread Aram Maliachi (WIPRO LIMITED)
ntire history that way. This is due to a limit set by the TFS product. -Original Message- From: git-ow...@vger.kernel.org On Behalf Of Aram Maliachi (WIPRO LIMITED) Sent: Friday, June 14, 2019 11:48 AM To: git@vger.kernel.org Cc: Kranz, Peter ; Brettschneider, Marco Subject: commit sized a

commit sized around 100 gb in changes failed to push to a TFS remote - Git

2019-06-14 Thread Aram Maliachi (WIPRO LIMITED)
To @Git Community >From the perspective of an Azure DevOps support engineer. I have a customer >who is unable to make a push with following error: fatal: The remote end hung up unexpectedly failed to push some refs into https://zelos.healthcare.siemens.com/tfs/Hoover/VA20A.DevInt.Gvfs/_git/Satur

change inside PR not reflected in the resulting squash commit

2019-05-31 Thread ARAM MALIACHI
I’m an Azure DevOps support engineer for Microsoft. Prior to composing this communication to the Git team I had a conversation with the Product Group from Azure DevOps stating this could be expected behavior, truth is they didn’t take the time to analyze this with me stating our PR system does noth