git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: git@vger.kernel.org
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	David Barr <david.barr@cordelta.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Tomas Carnecky <tom@dbservice.com>
Subject: Plans for the vcs-svn-pu branch
Date: Fri, 11 Feb 2011 03:09:31 -0600	[thread overview]
Message-ID: <20110211090931.GA27410@elie> (raw)
In-Reply-To: <20110105233915.GB22975@burratino>

(culled cc list for a new topic)
Hi,

Jonathan Nieder wrote:

> Here are the topics that are cooking in vcs-svn-pu.

Long time no pushout.  My old plan was to maintain a "vcs-svn" branch
and ask Junio to pull from it periodically.  I still plan to do that
since I think it's the only feasible way to roll out the larger
changes but I might be submitting smaller pieces as patches to the git
list directly.

The purpose of this email is to request help --- if you are
particularly interested in some subtopic then I would love to see a
patch series or pull request on the subject.  If I can forget about
vcs-svn-pu's existence and just review and accept ready-to-apply
patches on the topic as they come, then building a suitable vcs-svn
branch will become very, very simple.

The good news is that it's been a calm time, so most of these topics
are probably in good shape.

> * db/fast-import-blob-access (2011-01-03)
>  - fast-import: add 'ls' command

Needs a feature name.  Last seen at [1].

> * db/optimize-vcs-svn (2011-01-05) 9 commits
>  - vcs-svn: drop obj_pool.h
>  - vcs-svn: drop trp.h
>  - vcs-svn: drop string_pool
[...]

Applying this code removal early would make your local branch juggler
very, very happy.  Might make sense to pair it with some patches to
support cat-blob-fd in transport-helper's "import" support, so the UI
could be

	git fetch svn-dump::/tmp/file.dump

That could (perhaps) partially compensate for the loss of convenience
from requiring the cat-blob-fd to be plumbed correctly.  It's a shame
we weren't louder about svn-fe's command line usage being subject to
change.  Live and learn. :/

>  (this branch uses db/vcs-svn-incremental, db/text-delta, db/prop-delta,
>   jn/svndiff0, jn/sliding-window, jn/line-buffer, jn/line-buffer-error,
>   jn/line-buffer-large-file, and db/fast-import-blob-access.)

That's silly --- this long overdue cleanup does not require anything
except db/fast-import-blob-access.  Building it on top of
db/prop-delta seems okay, since the latter is simple and known to work
well.

> * db/vcs-svn-incremental (2011-01-05) 20 commits
[...]
>  (this branch uses db/text-delta, db/prop-delta, jn/svndiff0,
>   jn/sliding-window, jn/line-buffer, jn/line-buffer-error,
>   jn/line-buffer-large-file, and db/fast-import-blob-access.)
>
> Support for importing different revs in different svn-fe runs.

Killer feature.  After db/optimize-vcs-svn it is easy.  It does not
need to wait for Text-delta and svndiff0 support.

[...]

With those three topics out of the way, the rest of the wishlist
should be easy.  Most of the patches are already written.

 - line-buffer enhancements to support Text-delta (multiple buffers,
   sliding window, temporary files)
 - svndiff0 parser/interpreter
 - Text-delta support
 - Prop-delta support
 - support for large files
 - improved error handling
 - fast-import scalability fixes

  parent reply	other threads:[~2011-02-11  9:09 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
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       ` Jonathan Nieder [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110211090931.GA27410@elie \
    --to=jrnieder@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).