Re: Metadata and checkin file date

From: Jakub Narebski <jnareb@gmail.com>
Date: Apr 27, 2010, 21:18 UTC
Message-ID: <m3och4d27t.fsf@localhost.localdomain>
In-Reply-To: <4BD73F64.1070604@op5.se>

Andreas Ericsson <ae@op5.se> writes:

Show 18 quoted lines

> On 04/27/2010 09:38 PM, Gerhard Wiesinger wrote:
>> On Tue, 27 Apr 2010, Andreas Ericsson wrote:
>>> On 04/27/2010 07:23 AM, Gerhard Wiesinger wrote:
>>>>
>>>> I'm new to git and I'm looking for the following features:
>>>> 1.) Metadata for
>>>> a.) directory versioning (e.g. add/rm, mv)
>>>
>>> If you're talking about empty directories, that feature doesn't
>>> exist and I can't imagine why you'd want it to. If you'd care to
>>> explain why you want it, I'm sure we can find a different way of
>>> achieving your goal.
>> 
>> Git focuses on content but I think git should also focus on metadata. 
>> For example restructuring source code moves (git mv file1.c file2.c, git 
>> mv dir1 dir2) should be documented also in the repository like e.g. 
>> subversion and commercial SCM like clearcase do. Otherwise we are on 
>> "CVS" level.

"git mv file1.c file2.c" works in practice thanks to heuristic similarity based rename detection that git uses. (Note that it might not work in simplistic tests.)

"git mv dir1 dir2" works via _file_ rename detection, except for one use case, namely when on one branch one does "git mv dir1 dir2", and in other branch one does "git add dir1/file.c" (new file in old directory name). See also below.

Show 7 quoted lines

>> Empty directories is a special case and sometimes you need just 
>> versioned empty directies.
> 
> This has been discussed to death several times before on this mailing
> list. Browse the archives. There haven't been any new arguments the
> last 14 times it came up, so I doubt you'll be able to come up with
> a single good reason to track file renames explicitly.

There are three issues conflated here:

1. Rename tracking.  This is no go.  The only idea that have hint of
   being perhaps possibly accepted is recording resolutions of
   tree-level conflict in git-rerere2 cache.

2. Wholesame directory rename detection.  Possible, there were even
   some proof of concept patches send to git mailing list, but it
   didn't get merged in.  Would need to be resurrected, but this is
   not easy task.

3. Support for versioning empty directories.  Possible, but it would
   require extending index (the staging area one) to be able to hold
   not only files but also directories.  Not very easy.

   Current workaround: empty .gitignore / .keepme files.

-- 
Jakub Narebski
Poland
ShadeHawk on #git