From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 19 Sep 2015 12:40:11 -0700 (PDT) From: =?UTF-8?Q?Stefan_M=C3=BChlinghaus?= To: voidlinux Message-Id: <108e1462-365b-4b93-b8c7-c276eebc1bff@googlegroups.com> In-Reply-To: References: Subject: Re: howto to sqash files only on remote repo ? MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_315_1263026451.1442691611178" ------=_Part_315_1263026451.1442691611178 Content-Type: multipart/alternative; boundary="----=_Part_316_1037263944.1442691611179" ------=_Part_316_1037263944.1442691611179 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I am not an expert git user myself, but as far as I know using a new local branch with the squashed commits is the only feasable way to preserve your complete commit history. There may be other ways which would probably be even more tricky to use. Having a local and remote branch that differ in commits and are not supposed to be merged is simply not inteded git behaviour. ------=_Part_316_1037263944.1442691611179 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
I am not an expert git user myself, but as far as I know using a new local branch with the squashed commits is the only feasable way to preserve your complete commit history. There may be other ways which would probably be even more tricky to use.

Having a local and remote branch that differ in commits and are not supposed to be merged is simply not inteded git behaviour.
------=_Part_316_1037263944.1442691611179-- ------=_Part_315_1263026451.1442691611178--