From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rogan Dawes Subject: Re: Merge, rebase and whitespace fixes Date: Mon, 29 Jun 2009 23:30:47 +0200 Message-ID: <4A493287.20106@dawes.za.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Git List To: Giuseppe Bilotta X-From: git-owner@vger.kernel.org Mon Jun 29 23:32:15 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1MLOSU-0002yv-2P for gcvg-git-2@gmane.org; Mon, 29 Jun 2009 23:32:14 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753888AbZF2VcE (ORCPT ); Mon, 29 Jun 2009 17:32:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753283AbZF2VcC (ORCPT ); Mon, 29 Jun 2009 17:32:02 -0400 Received: from hapkido.dreamhost.com ([66.33.216.122]:34122 "EHLO hapkido.dreamhost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753059AbZF2VcA (ORCPT ); Mon, 29 Jun 2009 17:32:00 -0400 Received: from homiemail-a14.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by hapkido.dreamhost.com (Postfix) with ESMTP id CB5141842D5 for ; Mon, 29 Jun 2009 14:32:04 -0700 (PDT) Received: from artemis.local (dsl-246-34-245.telkomadsl.co.za [41.246.34.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a14.g.dreamhost.com (Postfix) with ESMTPSA id 682CC8C062; Mon, 29 Jun 2009 14:30:53 -0700 (PDT) User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Giuseppe Bilotta wrote: > Hello all, > > recently a tree I've been working on received some thorough whitespace > adjustments (changing indents from spaces to tabs). This results in > annoying conflicts when running merges or rebases with my local > branches. I tried googling around but I couldn't find any helpful > hints on how to make git cope with this. Any suggestions? > Do the same thing to your own tree?