Migration of services - 9. patchwork

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

 



Hi all,

the ninth on the list of services to migrate - patchwork - is more of a 
small trip into history. 


-- Migration status --

Is there any of you who remembers patchwork? Has anyone ever used it? The 
purpose of this service was to pick patches sent to the mailing list and 
allow them to be revised:

https://en.wikipedia.org/wiki/Patchwork_(software)

The service was on an old primary server, so it might appear to be the 
subject of migration. However, this service was probably never used and 
its purpose was completely replaced by TGW. Therefore, there is no reason 
to devote any effort to this service. Just a quiet memory.


-- What needs to be done --

You may have noticed that I have been talking about this service for the 
past. The reason is that the service is currently broken anyway - it 
returns code 500 - see https://patchwork.trinitydesktop.org/

So there is no need to do anything to migrate this service. At most, there 
can be a deleted DNS record.


-- More ideas and suggestions?

Does anyone have any objections or other suggestions?

Cheers
-- 
Slávek

Attachment: signature.asc
Description: This is a digitally signed message part.

____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx

[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux