From: Brian Norris <computersforpeace@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Bityutskiy,
Artem \(artem.bityutskiy@intel.com\)"
<artem.bityutskiy@intel.com>,
"David Woodhouse \(dwmw2@infradead.org\)" <dwmw2@infradead.org>,
patchwork@lists.ozlabs.org
Subject: Re: update patch state on patchwork
Date: Tue, 20 May 2014 12:32:58 -0700 [thread overview]
Message-ID: <20140520193258.GV28907@ld-irv-0074> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73EAC3B93@DBDE04.ent.ti.com>
Hi Pekon,
On Fri, Apr 18, 2014 at 09:15:03AM +0000, Pekon Gupta wrote:
> I was just wondering if there is a script which can automatically search the
> git tree and update state of patch on patchwork [1].
There is, sort of. Jeremy Kerr presented a few things at Linux Plumbers
a while back, and it includes a "catchup" script:
http://www.linuxplumbersconf.org/2011/ocw/system/presentations/255/original/patchwork.pdf
It marks "Accepted" patches based on the hash of the diff. There are
also git post-recevie hooks for updating automatically.
> If not then is it possible
> to update the patch status from now onwards (or may be a month back) ?
> This can be added as part of git-commit script used by Maintainers.
>
> This would be helpful in reviewing and finding references. And would be
> good for Maintainers too to keep a track of pending ones.
I've looked into your suggestion. I'm beginning to integrate Patchwork
into my workflow, and I'll see how it works out. I still have a few
kinks to work out (e.g., how to most easily mark patches as Superseded
when a new version is sent, for instance), but I have a few mutt and git
hooks established which help me in some of the major points. And I may
end up archiving much of the older stuff, just to start relatively
fresh.
Any tips for using patchwork to its fullest are welcome. I'm kind of in
a trial phase right now, where I'll see how much value patchwork can
add. If it really is just more work (on maintaining metadata) than it
helps, then I may not stick with it.
> [1] http://patchwork.ozlabs.org/project/linux-mtd/list/
Regards,
Brian
prev parent reply other threads:[~2014-05-20 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 9:15 update patch state on patchwork Gupta, Pekon
2014-05-20 19:32 ` Brian Norris [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=20140520193258.GV28907@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=artem.bityutskiy@intel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=patchwork@lists.ozlabs.org \
--cc=pekon@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox