Re: [PATCH 7/9] Add infrastructure to write revisions in fast-export format

Hi again,

Jonathan Nieder wrote:

repo_tree maintains the exporter's state and provides a facility to to
call fast_export, which writes objects to stdout suitable for
consumption by fast-import.

These files will also change significantly in a few days- see the
ternary_treap branch.

The exported functions roughly correspond to Subversion FS operations.

This description is sufficient for the commit message.

 . repo_add adds a file to the current commit.

 . repo_modify adds a replacement for an existing file;
  it is implemented exactly the same way, but a check could be
  added later to distinguish the two cases.

 . repo_copy copies a blob from a previous revision to the current
  commit.

 . repo_replace modifies the content of a file from the current
  commit, if and only if it exists.

 . repo_delete removes a file or directory from the current commit.

 . repo_commit calls out to fast_export to write the current commit to
  the fast-import stream in stdout.

 . repo_diff is used by the fast_export module to write the changes
  for a commit.

 . repo_reset erases the exporter's state, so valgrind can be happy.

This is like API documentation- should it go into the commit message?
Maybe put this in a a dedicated repo_tree.txt like trp.h?

-- Ram