You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Eric S. Raymond" <es...@thyrsus.com> on 2009/10/08 17:56:47 UTC
svncutter - Not planning to let the perfect be the enemy of the
good
Learning that svndumptool.py exists has confused my plans for
svncutter somewhat. My program does two things svndumptool.py doesn't,
"squash" and "setlog". The setlog function is pretty trivial, but getting
squash right is rather tricky. On the other hand, svndumptool.py is a much
more general tool with dozens of interesting capabilities mine
doesn't have.
In an ideal world, the code for squash and setlog would merge into
svndumptool.py (and svndumptool.py would become part of contrib/). Alas,
the svndumptool.py guy is not responding to email.
On the one hand, I don't want to put a lot more effort into svncutter
unless I know the merge isn't going to happen. I've suspended my plans
to write unit tests and the directory-lifting function that svndumptool.py
apparently duplicates. On the other hand, svncutter is a significant
improvement over svnsquash, and I'd prefer people actually got to use
it rather than having it gather dust on my hard drive.
Accordingly, I'm enclosing it to replace svnsquash in contrib/. I'll
continue trying to reach out and open a collaboration with the
svndumptool.py maintainer.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Re: svncutter - Not planning to let the perfect be the enemy of the
good
Posted by Mark Phippard <ma...@gmail.com>.
On Thu, Oct 8, 2009 at 2:04 PM, Mark Phippard <ma...@gmail.com> wrote:
> On Thu, Oct 8, 2009 at 1:56 PM, Eric S. Raymond <es...@thyrsus.com> wrote:
>> Learning that svndumptool.py exists has confused my plans for
>> svncutter somewhat. My program does two things svndumptool.py doesn't,
>> "squash" and "setlog". The setlog function is pretty trivial, but getting
>> squash right is rather tricky. On the other hand, svndumptool.py is a much
>> more general tool with dozens of interesting capabilities mine
>> doesn't have.
>
> I seem to recall that svndumptool.py does not work very well in many
> situations. If you Google it hasn't an svndumptool2 and svndumptool3
> been created to solve some of the problems? (It is possible I am
> confusing it with another tool). Also, I believe that one reason I
> think those tools were created is that the original author did not
> respond.
>
> If your tool does the same things and you are willing to maintain it,
> then I think you should move forward.
Grrr! I do not know why I sent that before Googling. I am confusing
this tool with svndumpfilter2. So never mind, and sorry to the
author.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2405238
Re: svncutter - Not planning to let the perfect be the enemy of the
good
Posted by Mark Phippard <ma...@gmail.com>.
On Thu, Oct 8, 2009 at 1:56 PM, Eric S. Raymond <es...@thyrsus.com> wrote:
> Learning that svndumptool.py exists has confused my plans for
> svncutter somewhat. My program does two things svndumptool.py doesn't,
> "squash" and "setlog". The setlog function is pretty trivial, but getting
> squash right is rather tricky. On the other hand, svndumptool.py is a much
> more general tool with dozens of interesting capabilities mine
> doesn't have.
I seem to recall that svndumptool.py does not work very well in many
situations. If you Google it hasn't an svndumptool2 and svndumptool3
been created to solve some of the problems? (It is possible I am
confusing it with another tool). Also, I believe that one reason I
think those tools were created is that the original author did not
respond.
If your tool does the same things and you are willing to maintain it,
then I think you should move forward.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2405231