All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Patchwork
Date: Wed, 7 Dec 2011 11:35:27 +0000	[thread overview]
Message-ID: <20111207113527.GA7389@linux-mips.org> (raw)

Account creation in patchwork was broken a long time ago and some unrelated
bug had caused a ugly junk in the listings of patches that contain
non-ASCII characters.  I've fixed both along with upgrading patchwork to
the latest and greatest version.

What this mean:

 - the junk names displayed in the listings is gone
 - you can create new patchwork accounts and use those accounts for example
   to administrate your own patches, for example when submitting a new
   version or when you discover a bug and want to withdraw a patch.

The upgrade went more than rough and involved lots of manual database
patching.  If something doesn't work right, please let me know.

Happy patchworking!

  Ralf

             reply	other threads:[~2011-12-07 11:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 11:35 Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-15 20:55 Patchwork Ryan Eatmon
2022-03-15 20:55 Patchwork Ryan Eatmon
2019-05-03 17:18 patchwork akuster808
2019-05-12 18:04 ` patchwork akuster808
2019-05-13  7:27   ` patchwork Zoran Stojsavljevic
2019-05-13  7:32   ` patchwork Mark Hatle
2019-04-17 10:17 patchwork John Crispin
2019-04-23 14:44 ` patchwork Kalle Valo
2019-04-23 14:49   ` patchwork Jeremy Kerr
2019-04-23 15:06     ` patchwork Kalle Valo
2019-05-06 12:53       ` patchwork Kalle Valo
2010-04-09  5:46 Initial work on an Android SDK via openembedded Angus Lees
2010-04-10 13:01 ` GNUtoo
2010-04-15 17:56   ` Patchwork Konrad Mattheis
2010-04-15 18:59     ` Patchwork Philip Balister
2009-11-11 14:55 Patchwork Ralf Baechle
2009-11-06 15:37 patchwork Chris Mason

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111207113527.GA7389@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.