netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Frank Pavlic <fpavlic@de.ibm.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/5] s390: qeth driver fixes
Date: Tue, 09 Jan 2007 08:45:44 -0500	[thread overview]
Message-ID: <45A39C88.5070606@pobox.com> (raw)
In-Reply-To: <20070109133922.GA21804@de.ibm.com>

Frank Pavlic wrote:
> Sorry for the trouble and also thank you very much
> for having done the extra work. I made the patches
> using git-format-patch so seems that I have to review
> them more carefully or I still haven't understand to use
> git-format-patch properly. 
> In any case I will read the documents you mentioned 
> once again to keep such points in mind...

If you are using git, maybe its as simple as checking in each patch with 
a unique first-line (== one-line summary)?

Also, if you so choose, you are welcome to submit changes directly via 
git to me, just like Martin Schwidefsky does with the main S/390 changes.

	Jeff




      reply	other threads:[~2007-01-09 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 16:29 [PATCH 1/5] s390: qeth driver fixes Frank Pavlic
2007-01-09  7:23 ` Jeff Garzik
2007-01-09 13:39   ` Frank Pavlic
2007-01-09 13:45     ` Jeff Garzik [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=45A39C88.5070606@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=fpavlic@de.ibm.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).