On Mon, May 28, 2012 at 03:35:47PM -0500, Jonathan Nieder wrote:
> (culling cc list)
> Thomas Dickey wrote:
> 
> > I have in mind creating a git-bundle using my fixed-up rcs-fast-export
> > (as an export-only...).
> 
> Thanks.  Please let me know when it's ready and I can publish it in
> the same place as the earlier export.

hmm.  I think it's more complicated than that.  I've created a git-bundle,
but it requires some discussion.  Here's a recap:

        + I spent a chunk of time in January working with rcs-fast-export,
          and setup a script to fixup the email addresses, to make the logs
          work as expected.  I modified rcs-fast-export to accept an option
          which makes it resolve the RCS identifiers properly.  (You may
          recall from earlier discussion that the identifiers _stored_ in
          the archive are from the previous data, rather than the actual
          revision).  That's slower to execute, of course.

        + In January I also worked (without much success) to develop a
          script to splice my changes onto a copy of the git bundle that
          you had published.  There is more than one apparent problem
          (aside from my own lack of git experience).  With or without
          the corrected RCS identifiers, the process fails due to merge
          problems.  I recall that this only gets about 60% through the
          import.  (I can of course provide you with the corresponding
          scripts, and we can discuss better approaches to the problem).

        + Not having progress on git (and having agreed to provide that),
          the dependent activities were stalled.  However, I'm back on
          mawk for a few weeks.  As I indicated, I noticed an interesting
          problem using mawk in a case where it's a matter of implementing
          a gawk-extension.

          I can see that extension would be a distraction (so I put it
          aside for the moment).

        + On a related thread, it was suggested that I get mawk into
          savannah for using bug-tracking.  When I investigated that,
          I noticed that they rather insist on having each file marked
          with copyrights.  Both Mike and I had not done that as rigorously
          as I think savannah wants.  So... I made that change on top of
          my 20101207 tag, calling that 20101210 (and kept the timestamps
          on that date to avoid confusing git further).  The tag is "old"
          of course since it's solely done to mark copyrights as of that
          date, and to avoid confusion with other changes that I have in
          mind.

          I put the mawk bundle for that in
                ftp://invisible-island.net/GIT/
          and uploaded that version as a new release on my webpage.
          
          I think those are enough pieces in place that I can followup on
          savannah; but have an idea that we need some discussion on how
          to proceed for your idea of providing patches based on git.
          (It would be nice if there were some way to record the transformation
          from my rcs/git archive into yours so that I could generate a better
          export).

-- 
Thomas E. Dickey <dic...@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature

Reply via email to