[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#924135: marked as done (clean-up: old .cvsignore files)

Your message dated Tue, 2 Apr 2019 19:12:43 +0200
with message-id <f00ae2aa-32c9-2e33-0134-4afcb4bc311a@debian.org>
and subject line clean-up: old .cvsignore files and stuff used with CVS only
has caused the Debian Bug report #924135,
regarding clean-up: old .cvsignore files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

924135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924135
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: www.debian.org
Severity: normal
User: www.debian.org@packages.debian.org
Usertags: scripts


While working on rebuilding the website within stretch and buster, I've
noticed the following.

There are many leftovers from CVS times in the tree, namely .cvsignore

    $ find -name .cvsignore|sort

It might make sense to merge some of it into .gitignore, but getting rid
of them in the end would make sense I suppose.

Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

--- End Message ---
--- Begin Message ---
Hello all
I have removed all the stuff related to CVS, both in webwml and in the
cron repos.
I have moved all the exceptions that were included in .cvsignore files
to the corresponding .gitignore files and removed the .cvsignore files

I have added some more exceptions pointed out in Thomas' last email.

I think this bug can be closed, if you spot anything that remains to be
done, feel free to reopen.

Kind regards,
Laura Arjona Reina

--- End Message ---

Reply to: