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

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Jun 24, 2010, 19:49 UTC
Message-ID: <20100624194927.GB2065@burratino>
In-Reply-To: <AANLkTikyjq7HQY1hUTOGF_oBsGDj_jUI-GwDBRdacCzG@mail.gmail.com>

On Thu, Jun 24, 2010 at 09:29:29PM +0200, Ramkumar Ramachandra wrote:

> Jonathan Nieder wrote:

>>  . repo_reset erases the exporter's state, so valgrind can be happy.
> 
> This is like API documentation- should it go into the commit message?

A more terse summary, to save readers time:

 . repo_add, repo_modify, repo_copy, repo_replace, and repo_delete
   update the current commit, based roughly on the corresponding
   Subversion FS operation.

 . 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.

Jonathan