From: Hannes Reinecke <hare@suse.de>
To: Christophe Varoqui <christophe.varoqui@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: SUSE multipath-tools resync
Date: Thu, 05 May 2011 09:37:54 +0200 [thread overview]
Message-ID: <4DC253D2.1090907@suse.de> (raw)
Hi Christophe,
I'm currently rebasing my multipath-tools git tree to the latest
upstream version and planning on sending out the missing patches.
However, I found that I should've done that far earlier; so far I've
accumulated about 40-odd patches and I'm only halfway through the
resulting diff :-(
How do you prefer those patches? Should I send them off in one bulk
or rather several smaller batches?
Most of them are totally unrelated, just various fixes here and
there. So it doesn't really matter in which order they'll be applied.
Only some patches are for infrastructure changes :-)
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
reply other threads:[~2011-05-05 7:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DC253D2.1090907@suse.de \
--to=hare@suse.de \
--cc=christophe.varoqui@gmail.com \
--cc=dm-devel@redhat.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.