[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The fixes-bug field
From: |
Eric S. Raymond |
Subject: |
Re: The fixes-bug field |
Date: |
Thu, 16 Jan 2014 13:08:09 -0500 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Eli Zaretskii <address@hidden>:
> I think we should decide on how to store this info and how to report
> the fixed bugs once we switch to git, before we decide on how to
> convert this data from bzr, and whether or not this justifies a new
> conversion from scratch rather than reuse of the existing mirror.
My tentative plan is to append a report of the fixes property to each
log message that has it.
In order to fix up commit references, I'm going to have to build a small
database that maps Bazaar revnos to action stamps. That in turn I will
use to generate a sequence of reposurgeon commands that will patch up
the repository content. For the curious, an example command would look
like this:
[ChangeLog] filter --regex /revno 108687/2012-06-13T21:07:address@hidden/
except I'll probably add a --replace modifier to the reposurgeon
filter command that avoids the regexp overhead.
Building that database already requires parsing the output of bzr log.
Since I have to do that anyway, parsing the fixes-bug property and
associating it with the revno is not much more work. I'll generate
commands that append each report to the proper commit (the
equivalent of the rewriter someone else mentioned).
All these commands, together with several hundred tag names and deletes,
will go into a reposurgeon script that I run on conversion day.
I also plan, by the way, to run a coalescence pass. There are cliques of
formerly-CVS commits with identical messages that didn't get properly
merged when Andreas did the CVS lift, probably because the merge time window
was set too small. (This is *very* common in CVS conversions.)
Yes, preparing for this will be a lot of work. Welcome to the difference
between a crappy conversion done with weak tools and a really high-quality
lift done with good tools and craftsmanlike attention to the individual
project history.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
- Re: The fixes-bug field, (continued)
- Re: The fixes-bug field, Glenn Morris, 2014/01/16
- Re: The fixes-bug field, Eric S. Raymond, 2014/01/16
- Re: The fixes-bug field, Darren Hoo, 2014/01/16
- Re: The fixes-bug field, Stefan Monnier, 2014/01/16
- Re: The fixes-bug field, Glenn Morris, 2014/01/16
- Re: The fixes-bug field, Eli Zaretskii, 2014/01/16
- Re: The fixes-bug field, Eli Zaretskii, 2014/01/16
- Re: The fixes-bug field, Paul Eggert, 2014/01/16
- Re: The fixes-bug field, Glenn Morris, 2014/01/16
- Re: The fixes-bug field, Paul Eggert, 2014/01/16
- Re: The fixes-bug field,
Eric S. Raymond <=
- Re: The fixes-bug field, Eli Zaretskii, 2014/01/16
- Re: The fixes-bug field, Eric S. Raymond, 2014/01/16
- Re: The fixes-bug field, Eli Zaretskii, 2014/01/16
- Re: The fixes-bug field, Eric S. Raymond, 2014/01/16
- Re: The fixes-bug field, Eli Zaretskii, 2014/01/17
- Re: The fixes-bug field, Paul Eggert, 2014/01/17
- Re: The fixes-bug field, Jarek Czekalski, 2014/01/17
- Re: The fixes-bug field, Yuri Khan, 2014/01/17
- Re: The fixes-bug field, Stefan Monnier, 2014/01/17
- Re: The fixes-bug field, Lars Ingebrigtsen, 2014/01/17