Hi Pino,

On Sun, Apr 15, 2018 at 08:09:19PM +0200, Pino Toscano wrote:
> > I am ready to push them to Salsa at any moment, and I have updated my
> > import [1] to the latest revision recently, but Pino (CCed) asked me to
> > wait a bit more until he reviews it.
> How where they converted? Where are the scripts/rules used for them?


> > [1]: https://anonscm.debian.org/git/users/mitya57/kde-extras/
> I am now sure which criterias you chose, but these repositories include
> stuff not present in Debian, some of them removed many years ago, and
> few even things never uploaded...

Ok, I will remove repositories that are neither in stable nor in sid.

> <grumpy>why am I poked to review stuff that makes no sense to
> convert? why do *I* have to check even this?</grumpy>

I asked you to review just your repos, not *everything* :)

> I'd say:
> - start with sources currently in unstable/testing (so stuff that most
>   probably will get more work), in batches of 10 (so it can be reviewed
>   more easily)
> - after that, go on to sources in stable but no more in unstable, since
>   they might get changes in stable
> - then decide what to do about the rest

As said above, I will do a bit more cleanup.

> Random things I found out:
> * there are tags backups/$oldbranchname@$revision, which should be
>   checked whether they makes sense as branch names instead, or just
>   drop them otherwise
> * rsibreak:
>   - the tag debian/0.9.0_beta3 with no parents nor children

Because it was created in an unusual way:

“move old kde4 packaging to a tag”

>   - there are two initial empty commits

The conversion script creates a Git commit for every Svn commit.
Is this really a problem?

>   - the branch upstream has basically only empty commits

Good catch, I will delete upstream branches.

> * kmplayer:
>   - the branch experimental (that merges to master) starts from nothing

Again, it is an issue with the original SVN repo. The directory was
created, not copied from trunk:

> and I did not check more than other 10 repositories or so.

Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


Reply via email to