From mboxrd@z Thu Jan  1 00:00:00 1970
From: nn6eumtr <nn6eumtr@gmail.com>
Subject: Re: How to deal with historic tar-balls
Date: Fri, 06 Jan 2012 20:10:57 -0500
Message-ID: <4F079BA1.3060907@gmail.com>
References: <4EFF5CDA.5050809@gmail.com> <4F05C0E2.4050101@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: Neal Kreitzinger <nkreitzinger@gmail.com>, git@vger.kernel.org
X-From: git-owner@vger.kernel.org Sat Jan 07 02:11:02 2012
Return-path: <git-owner@vger.kernel.org>
Envelope-to: gcvg-git-2@lo.gmane.org
Received: from vger.kernel.org ([209.132.180.67])
	by lo.gmane.org with esmtp (Exim 4.69)
	(envelope-from <git-owner@vger.kernel.org>)
	id 1RjKoH-0004rP-Ls
	for gcvg-git-2@lo.gmane.org; Sat, 07 Jan 2012 02:11:02 +0100
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1759058Ab2AGBK5 (ORCPT <rfc822;gcvg-git-2@m.gmane.org>);
	Fri, 6 Jan 2012 20:10:57 -0500
Received: from mail-qy0-f174.google.com ([209.85.216.174]:65459 "EHLO
	mail-qy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1758826Ab2AGBK4 (ORCPT <rfc822;git@vger.kernel.org>);
	Fri, 6 Jan 2012 20:10:56 -0500
Received: by qcqz2 with SMTP id z2so1226289qcq.19
        for <git@vger.kernel.org>; Fri, 06 Jan 2012 17:10:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=ZFTQygJM3Xm/NxRxC7j41K0TZ82NAqpjlpmNYECJRlI=;
        b=R1E6/PqTGyzn4XAWa+RgwwandaYYlnum11qvIc0otOAxTFlR5+9ZdD/kdvB2Gg9SWB
         AtdKyQwnkjQhwWvvNB+OU1hLJSRNHNxmIrlFZH0FJnf8mNIemILIGvvIhMdHoX5YCUkM
         3YEFB4ZwXrAVLg/WhfDg4DzF8MT8gbTMzXT4U=
Received: by 10.224.178.207 with SMTP id bn15mr10644124qab.34.1325898655719;
        Fri, 06 Jan 2012 17:10:55 -0800 (PST)
Received: from [192.168.0.7] (cpe-24-90-181-153.nyc.res.rr.com. [24.90.181.153])
        by mx.google.com with ESMTPS id ft9sm125599237qab.20.2012.01.06.17.10.54
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 06 Jan 2012 17:10:54 -0800 (PST)
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
In-Reply-To: <4F05C0E2.4050101@gmail.com>
Sender: git-owner@vger.kernel.org
Precedence: bulk
List-ID: <git.vger.kernel.org>
X-Mailing-List: git@vger.kernel.org
Archived-At: <http://permalink.gmane.org/gmane.comp.version-control.git/188058>

Thanks for the response, there is lots of good information there.

One clarification - can you track renames in git? I tried using git mv 
but from the status output it looks like it deleted the old file  and 
added the new file. I was expecting it to record some sort of indicator 
of the name change, instead it looks like a short-cut for delete & add, 
the docs aren't clear if that is the case.

On 1/5/2012 10:25 AM, Neal Kreitzinger wrote:
...
> going to want to do appropriate clean up of the working tree in each
> iteration before committing. This is where you would review
> renames/removes with git-status before you git-add and git-commit. Also,
> if you are tracking permissions in git (the executable bit) then you
> will want to filter out any noise generated by frivolous permissions
> changes between the tarball contents.
...