| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
From FS#29922, indicate what happens if the package is unmaintained.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Touch up the style slightly on the flag help popup to match the main
site style more closely.
When a logged-in user is flagging a package out of date, we have no need
for them to fill in the email field since we already have an email
address on file.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
We already use HTTPS exclusively for wiki, bugs, forums, etc. and we
have it available for our other sites, so link only to the https://
protocol locations when pointing users at other sites.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Since we only do HTTPS now on these services, no point in sending someone
through a useless redirect.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
* better semantics
* consistent appearance with archweb theme
* descriptive href titles
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
Random stupids in our HTML, this should be a little better at least.
Signed-off-by: Dan McGee <dan@archlinux.org>
|
|
|
|
Flagging a package out of date is not needed in the backend. Backend only needs
to unflag.
|
|
Special Note
Prior to git import, approx 90% of the code was done by Judd Vinet. Thanks Judd!
|
