libwv2-0.4.2 release

[cricketc]

New release of libwv2-0.4.2. Grab it from SourceForge.

Maybe this will be the last individual release of wv2, if we move it koffice
svn. The current svn repository only has 44 revisions, since I moved it from
cvs without importing all the history. Should we just make one commit into the
koffice svn, or does someone want to try to import history as well?

-Benjamin
_______________________________________________
koffice-devel mailing list
koffice-devel@...
https://mail.kde.org/mailman/listinfo/koffice-devel

[Werner Trobin]

On Sunday 01 November 2009 02:58:53 cricketc@... wrote:
> New release of libwv2-0.4.2. Grab it from SourceForge.
>
> Maybe this will be the last individual release of wv2, if we move it
> koffice svn. The current svn repository only has 44 revisions, since I
> moved it from cvs without importing all the history. Should we just make
> one commit into the koffice svn, or does someone want to try to import
> history as well?

In a perfect world, the CVS history as well as the current (short) SVN history
would be moved to the KOffice repository. In case KOffice switches to git
soon, this should probably be done after the move to git, since the git
importing tools seem to be slightly more flexible than the SVN ones.

Ciao,
Werner

_______________________________________________
koffice-devel mailing list
koffice-devel@...
https://mail.kde.org/mailman/listinfo/koffice-devel

[cricketc]

On Sunday 01 November 2009 03:37:20 Werner Trobin wrote:

> On Sunday 01 November 2009 02:58:53 cricketc@... wrote:
> > New release of libwv2-0.4.2. Grab it from SourceForge.
> >
> > Maybe this will be the last individual release of wv2, if we move it
> > koffice svn. The current svn repository only has 44 revisions, since I
> > moved it from cvs without importing all the history. Should we just make
> > one commit into the koffice svn, or does someone want to try to import
> > history as well?
>
> In a perfect world, the CVS history as well as the current (short) SVN
>  history would be moved to the KOffice repository. In case KOffice switches
>  to git soon, this should probably be done after the move to git, since the
>  git importing tools seem to be slightly more flexible than the SVN ones.

Yup, in a perfect world we would keep all the history. :) If anyone wants to
import the history into the koffice repo, you are welcome to do so - please
speak up and go for it. Otherwise, if no one will do it, I can add all the
files in one large commit.

-Benjamin
_______________________________________________
koffice-devel mailing list
koffice-devel@...
https://mail.kde.org/mailman/listinfo/koffice-devel

On Sunday 01 November 2009, cricketc@... wrote:

> On Sunday 01 November 2009 03:37:20 Werner Trobin wrote:
> > On Sunday 01 November 2009 02:58:53 cricketc@... wrote:
> > > New release of libwv2-0.4.2. Grab it from SourceForge.
> > >
> > > Maybe this will be the last individual release of wv2, if we move it
> > > koffice svn. The current svn repository only has 44 revisions, since I
> > > moved it from cvs without importing all the history. Should we just
> > > make one commit into the koffice svn, or does someone want to try to
> > > import history as well?
> >
> > In a perfect world, the CVS history as well as the current (short) SVN
> >  history would be moved to the KOffice repository. In case KOffice
> > switches to git soon, this should probably be done after the move to git,
> > since the git importing tools seem to be slightly more flexible than the
> > SVN ones.
>
> Yup, in a perfect world we would keep all the history. :) If anyone wants
>  to import the history into the koffice repo, you are welcome to do so -
>  please speak up and go for it. Otherwise, if no one will do it, I can add
>  all the files in one large commit.

Maybe we can just commit everything without the history -- the history is
available on sourceforge and won't disappear. We could always add the history
retroactively once KOffice has moved to git.

--
Boudewijn Rempt | http://www.valdyas.org
_______________________________________________
koffice-devel mailing list
koffice-devel@...
https://mail.kde.org/mailman/listinfo/koffice-devel