git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Cc: David Michael Barr <david.barr@cordelta.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Daniel Shahaf <daniel@shahaf.name>
Subject: [GSoC update] git-remote-svn: Week 8
Date: Wed, 23 Jun 2010 18:22:13 +0200	[thread overview]
Message-ID: <1277310140-16891-1-git-send-email-artagnon@gmail.com> (raw)

Hi,

I've been very productive over the last few days. The good news is
that I finally managed to a (badly-formatted, broken, abridged) dump
of the text and properties. The bad news is that the program only
seems to work by accident- it segfaults all over the place without
reason, I don't know what to make of the backtraces, and documentation
is thin as usual. I plan to go back in history to do a major cleanup/
refactor before proceeding, now that I've learnt how to trigger the
dumping.
 
I got this far mainly because of the help I got from Subversion
developers like Daniel- A big thank you to them. The plan is to finish
this, get it reviewed/ acked by Daniel and the other Subversion
developers, and test it with David's exporter before merging it into
git.git. Once it's merged, I plan to write a series for Subversion,
get it merged there, and remove it from git.git in favor of simply
linking to the feature. The reason for this roundabout dance is
simple- things are much easier to test in Git-land.

Another thing that I think we should give some thought- how do I get
this merged into git.git? Should I post a single patch with the
(probably 1000-line) dump editor? In my opinion, the revision history
is very valuable- can we get a clean series of 6~8 patches merged
instead?

-- Ram

Ramkumar Ramachandra (7):
  Add skeleton RA svnclient
  Add stripped dump editor
  Import dump_node to dump what changed and cleanup whitespace
  Replace deprecated svn_path_join
  Trigger dump_node in change_dir_prop
  Add file_baton and trigger dump_node in change_file_prop
  [WIP] Dump the text delta

 LICENSE        |   14 ++
 Makefile       |    4 +
 debug_editor.c |  413 +++++++++++++++++++++++++++++++++++
 debug_editor.h |    6 +
 dump_editor.c  |  652 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 dump_editor.h  |   10 +
 svnclient_ra.c |  138 ++++++++++++
 7 files changed, 1237 insertions(+), 0 deletions(-)
 create mode 100644 LICENSE
 create mode 100644 Makefile
 create mode 100644 debug_editor.c
 create mode 100644 debug_editor.h
 create mode 100644 dump_editor.c
 create mode 100644 dump_editor.h
 create mode 100644 svnclient_ra.c

             reply	other threads:[~2010-06-23 16:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 16:22 Ramkumar Ramachandra [this message]
2010-06-23 16:22 ` [WIP PATCH 1/7] Add skeleton RA svnclient Ramkumar Ramachandra
2010-06-25  0:14   ` Jonathan Nieder
2010-06-25  9:07     ` Daniel Shahaf
2010-06-25 11:07       ` Ramkumar Ramachandra
2010-06-25 11:30         ` Daniel Shahaf
2010-06-25 15:30           ` OT: typesafe callbacks in C (Re: [WIP PATCH 1/7] Add skeleton RA svnclient) Jonathan Nieder
2010-06-25 14:45         ` [WIP PATCH 1/7] Add skeleton RA svnclient Jonathan Nieder
2010-06-25 13:34       ` Jonathan Nieder
2010-06-23 16:22 ` [WIP PATCH 2/7] Add stripped dump editor Ramkumar Ramachandra
2010-06-23 16:22 ` [WIP PATCH 3/7] Import dump_node to dump what changed and cleanup whitespace Ramkumar Ramachandra
2010-06-23 17:05   ` Ramkumar Ramachandra
2010-06-23 16:22 ` [WIP PATCH 4/7] Replace deprecated svn_path_join Ramkumar Ramachandra
2010-06-23 16:22 ` [WIP PATCH 5/7] Trigger dump_node in change_dir_prop Ramkumar Ramachandra
2010-06-23 16:22 ` [WIP PATCH 6/7] Add file_baton and trigger dump_node in change_file_prop Ramkumar Ramachandra
2010-06-23 16:22 ` [WIP PATCH 7/7] Dump the text delta Ramkumar Ramachandra
2010-06-23 17:18 ` [GSoC update] git-remote-svn: Week 8 Ramkumar Ramachandra
2010-06-25  0:42   ` Jonathan Nieder

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=1277310140-16891-1-git-send-email-artagnon@gmail.com \
    --to=artagnon@gmail.com \
    --cc=daniel@shahaf.name \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=srabbelier@gmail.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 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 NNTP newsgroup(s).