Re: git repository with fixed history ready

[Carl Sorensen]

On 3/22/10 7:49 PM, "Graham Percival" <address@hidden> wrote:

> On Mon, Mar 22, 2010 at 09:18:40AM +0100, Jan Nieuwenhuizen wrote:
>> There's one small problem with replacing the old repository,
>> *all* committishes change, and everyone will have to make
>> a fresh clone, and any work based on the old repository
>> must be copied over to the new clone using git format-patch
>> and git am.
> 
> Could somebody translate for the git-impaired?
> 
> - if I have no non-pushed commits, do I need to do anything?

No.

> 
> - does anything need to happen to branches like dev/waf ?  (again,
>   assuming that we have pushed everything)

No.

> 
> - if we tell new contributors to remove their lilypond-git dirs
>   before the changeover, then tell them to run lily-git after the
>   changeover, will it work?

Yes.

If a user has *non-pushed* branches, then the proper way to deal with it,
IIUC, is to clone a new repository.  Then create a branch from the
equivalent commit in the new repository.  Create a patch in the old
repository, and apply the patch to the new repository.

But for people who don't have *non-pushed* branches around, it should be no
problem.

Carl