Re: fast-import tweaks for remote helpers (Re: Status of the svn remote helper project (Dec 2010, #1))

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 12/12/10 19:14, Jonathan Nieder wrote:
That's good to hear. What should be the syntax for asking fast-import
not to write to a ref?  Something like this?

	commit
	mark :1
	committer c o mitter<committer@xxxxxxxxxxx>  now
	data<<END
	...

Writing the sha1 as each commit is written: how early does the
frontend need access to the sha1?  Would a facility to report marks
back to the frontend at the end of the stream take care of it?

What happened to --report-fd ?

(In the back of my mind, I have the idea of using a
file that allows O(1) access, perhaps of the form

	<commit name for rev 1>  NL
	<commit name for rev 2>  NL
	...

This doesn't scale to many branches; git-svn started with that and had to use a b-tree in the end. Eg, consider a repository with 10,000 branches and 600,000 revisions.

Thanks for continuing this work, it is most interesting to follow.

Cheers,
Sam
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]