All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Archive old patches on "Patchwork XFS Filesystem from SGI"
Date: Fri, 25 Oct 2013 12:56:01 -0500	[thread overview]
Message-ID: <526AB0B1.1060701@sgi.com> (raw)
In-Reply-To: <526A88B7.3010007@sandeen.net>

On 10/25/2013 10:05 AM, Eric Sandeen wrote:
> On 10/25/13 8:17 AM, Rich Johnston wrote:
>> Hey Folks,
>>
>> SGI uses Patchworks (http://patchwork.xfs.org/project/XFS/list/) to track XFS patches.  I would like to archive any patches 6 months or older. They should be reworked and resubmitted.
>>
>> Archived patches are not deleted and can be viewed by changing the default "Archived" checkbox from "No" to "Yes" or "Both".
>>
>> If there are any objections please speak up.
>
> It's a bit of a mess by now, so maybe it is best to reset.
Glad you agree. :)
>
> Is there a newer patchworks available?  For example I was wondering the other day if there is any mechanism to automatically change patch state based on "Reviewed-by's" sent to the list.
Yes there is a newer version but I don't see that it would help to upgrade.
>
> I also was surprised that there's no way to search by patch author - I wanted to find my old outstanding patches, and it wasn't super-easy.
You can sort by submitter, does that help? ;)
>
> -Eric
>
>> Thanks
>> --Rich
>

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2013-10-25 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 13:17 Archive old patches on "Patchwork XFS Filesystem from SGI" Rich Johnston
2013-10-25 15:05 ` Eric Sandeen
2013-10-25 17:56   ` Rich Johnston [this message]

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=526AB0B1.1060701@sgi.com \
    --to=rjohnston@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /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.