Re: git-svn and huge data and modifying the git-svn-HEAD branch directly

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Mar 1, 2006, 21:40 UTC
Message-ID: <46a038f90603011340k23327f11s6e3d9d69585a5188@mail.gmail.com>
In-Reply-To: <7virqyf094.fsf@assigned-by-dhcp.cox.net>

On 3/2/06, Junio C Hamano <junkio@cox.net> wrote:

Show 6 quoted lines

> Linus Torvalds <torvalds@osdl.org> writes:
>
> > But if somebody does the get_sha1() magic, and Junio agrees, then I think
> > it would be a great thing to do.
>
> I am inclined to agree here.

Aren't we doing a lot of work (changes in core git, and corresponding changes in the porcelain) when simple changes in porcelain would suffice? Let's imagine that

 - git-commit refuses to commit to a head that has a corresponding
remote (cg-commit does this already with heads that match something in
'branches')
 - git-$SCMimport scripts generate a semi-bogus remotes/headname entry
 - git-pull/push can spot and ignore the semi-bogus remotes/headname entry
 - this means that `touch remotes/foo` is now a cheap way of making
the head readonly
 - depending on the git-$SCMimport script, the remotes/headname file
can perhaps contain useful configuration data for the import, so
git-$SCMimport headname does the right thing.

cheers,

martin