Re: Question about handling of heterogeneous repositories

From: Alex Riesen <raa.lkml@gmail.com>
Date: Nov 30, 2005, 15:01 UTC
Message-ID: <81b0412b0511300701w71da125am2dcc896b4693f37f@mail.gmail.com>
In-Reply-To: <200511301540.34776.Josef.Weidendorfer@gmx.de>

On 11/30/05, Josef Weidendorfer <Josef.Weidendorfer@gmx.de> wrote:

Show 6 quoted lines

> git-mv could support this. Additional to deleting from
> one repository and adding to the new, it could generate a remark for
> the commit message, like:
>
>  Added file xxx is from remote repo '/path/myrepo' with name 'yyy'
>  (file SHA1: 123445... from remote commit SHA1: 345667...)

That's sounds very tempting to special-case for nested repos :)

Maybe use .git/objects/info/alternates in top-level repo? It may
have side-effects of the new objects ending up in top-level repo
if commited from top-level directory. Even then, the tools can
be tought to stop looking for GIT_DIR in the directory closest
to the file being commited:
  $ pwd
  .../top
  $ git-commit sub1/dir/file
  ... uses repo in .../top/sub1 instead of $(pwd)/../top/.git

Looks very messy, with a potential for lots of corner cases and not that tempting anymore :(

> This info could be interesting both for humans and a history browsing tool.
> The tool still would have to know where to look for repo '/path/myrepo'.
> It could also work for moving subdirectories (ie. trees instead of files).

Well, these are just lots of files. I can't really think of case were I'd need to know about moving a directory without knowing what happened to the files.

>
> Josef
>