From: Sam Vilain <sam@vilain.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Tomas Carnecky <tom@dbservice.com>,
git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
David Barr <david.barr@cordelta.com>, Sam Vilain <sam@vilain.net>,
Stephen Bash <bash@genarts.com>
Subject: Re: fast-import tweaks for remote helpers (Re: Status of the svn remote helper project (Dec 2010, #1))
Date: Sun, 12 Dec 2010 22:53:41 +1300 [thread overview]
Message-ID: <4D049BA5.1060509@vilain.net> (raw)
In-Reply-To: <20101212061437.GA17185@burratino>
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@example.com> 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
next prev parent reply other threads:[~2010-12-12 10:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 11:21 Status of the svn remote helper project (Nov, 2010) Jonathan Nieder
2010-11-07 12:06 ` David Michael Barr
2010-11-08 3:56 ` David Barr
2010-11-08 6:11 ` Jonathan Nieder
2010-11-08 6:20 ` David Barr
2010-11-07 12:50 ` Ramkumar Ramachandra
2010-11-07 17:42 ` Jonathan Nieder
2010-11-21 6:31 ` Status of the svn remote helper project (Nov 2010, #2) Jonathan Nieder
2010-11-21 9:38 ` David Michael Barr
2010-11-21 23:06 ` Jonathan Nieder
2010-11-22 2:06 ` David Barr
2010-12-05 11:37 ` Status of the svn remote helper project (Dec 2010, #1) Jonathan Nieder
2010-12-08 18:26 ` Tomas Carnecky
2010-12-12 6:14 ` fast-import tweaks for remote helpers (Re: Status of the svn remote helper project (Dec 2010, #1)) Jonathan Nieder
2010-12-12 9:53 ` Sam Vilain [this message]
2010-12-12 17:16 ` fast-import tweaks for remote helpers Jonathan Nieder
2011-01-05 21:20 ` fast-import --report-fd (Re: fast-import tweaks for remote helpers) Jonathan Nieder
2011-01-05 23:39 ` Status of the svn remote helper project (Jan 2011, #1) Jonathan Nieder
2011-01-07 14:00 ` David Michael Barr
2011-02-11 9:09 ` Plans for the vcs-svn-pu branch Jonathan Nieder
2011-02-11 10:36 ` [PATCH] svn-fe: warn about experimental status Jonathan Nieder
2011-02-11 15:49 ` Plans for the vcs-svn-pu branch Ramkumar Ramachandra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D049BA5.1060509@vilain.net \
--to=sam@vilain.net \
--cc=artagnon@gmail.com \
--cc=bash@genarts.com \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=srabbelier@gmail.com \
--cc=tom@dbservice.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.