creating the arpwatch repo

[Raphael Hertzog]

On Sun, 09 Apr 2017, Lukas Schwaighofer wrote:
> I worked around that by temporarily disabling the commit hook to get
> the repository in the "old" state (i.e. similar to what it is on
> collab-maint currently), and then re-enabled it before pushing my own
> changes. They were still more than 20 commits, so no commit mails were
> sent out, but bugs that are fixed by my upload have been tagged as
> pending in the BTS as they should.
> 
> If somebody knows (for future reference), I would still like to know if
> it would have been "safe" to push with the hook enabled.

The number of commit emails sent is limited so that part would have been
safe. About having more bugs tagged as pending, I don't think that would
have been very problematic...

Another solution would have been to copy the repository directly from
/git/collab-maint/ on git.debian.org and thus entirely avoiding the need
to go through git to upload the history. You would then have to manually
configure the hooks and rename some branches but that's it.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/