All of lore.kernel.org
 help / color / mirror / Atom feed
From: moon.linux@yahoo.com (Anand Moon)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Download patch from email.
Date: Sun, 15 Feb 2015 04:44:00 +0000 (UTC)	[thread overview]
Message-ID: <1620069054.5620255.1423975440910.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <20150214090457.GA5140@myarchbang>

Hi Silvan,

Thanks for your input. 


I got following link which could be uses full for beginner.

`pwclient` can be used for example to retrieve patches, search the queue or update the state. 

http://www.openembedded.org/wiki/Patchwork
http://www.linuxplumbersconf.org/2011/ocw/system/presentations/255/original/patchwork.pdf

-Anand Moon


On Saturday, February 14, 2015 2:38 PM, Silvan Jegen <me@sillymon.ch> wrote:
On Sat, Feb 14, 2015 at 03:48:53AM +0000, Anand Moon wrote:

> I have configured mutt as email client.
> 
> https://github.com/narkoleptik/dotfiles/blob/master/.muttrc
> 
> But my configuration don't allow me to download Linux patch's from
> email.

I use mutt's standard functionality to get patches from emails which I
did not have to configure IIRC. Depending on whether the patches have
been sent inline (within the email text itself) or attached to the email
I use two different methods.

Inline patches:
I use 'C' (if there are multiple patches you can tag all the mail
messages first and then use ';C') to copy all the mail messages to a
mailbox file. This mailbox file can then be read by the 'git am' command
which applies all the patches (including the commit messages) to your
git tree.

Attached patches:
Select the mail message, click 'v' and save the attached patches to disk
with 's'.

Hope that helps. I would like to hear if other people have more
efficient workflows (using custom scripts for example)!


Cheers,

Silvan


_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2015-02-15  4:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-14  3:48 Download patch from email Anand Moon
2015-02-14  9:04 ` Silvan Jegen
2015-02-15  4:44   ` Anand Moon [this message]
2015-02-15  6:11   ` Elazar Leibovich
2015-02-15  9:30     ` Silvan Jegen
2015-02-15 16:48       ` Anand Moon

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=1620069054.5620255.1423975440910.JavaMail.yahoo@mail.yahoo.com \
    --to=moon.linux@yahoo.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.