netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: Danny van Dyk <kugelfang-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: "John W. Linville"
	<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: [GIT PULL] bcm43xx: Update B6PHY initialization
Date: Tue, 31 Jan 2006 19:21:01 -0500	[thread overview]
Message-ID: <20060201002101.GA8306@havoc.gtf.org> (raw)
In-Reply-To: <43DFFB6C.9050907-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

On Wed, Feb 01, 2006 at 01:06:04AM +0100, Danny van Dyk wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi John,
> 
> I'm slowly trying to get accustomed to git, so I'll try a short patch
> as a first step. So please
> 
> git pull rsync://pitr.amd64.dev.gentoo.org/kugelfang/wireless-2.6.git

Your git pull email needs to include a summary of included changesets,
and a patch for others to review.

	Jeff

  parent reply	other threads:[~2006-02-01  0:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01  0:06 [GIT PULL] bcm43xx: Update B6PHY initialization Danny van Dyk
     [not found] ` <43DFFB6C.9050907-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-02-01  0:21   ` Jeff Garzik [this message]
     [not found]     ` <20060201002101.GA8306-oTNwCEtKUwI/11+TDStg7g@public.gmane.org>
2006-02-01  9:51       ` Danny van Dyk
     [not found]         ` <200602011051.00973.kugelfang-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-02-01 13:55           ` Michael Buesch
     [not found]             ` <200602011455.34307.mbuesch-KuiJ5kEpwI6ELgA04lAiVw@public.gmane.org>
2006-02-01 18:54               ` Danny van Dyk
     [not found]                 ` <200602011954.52325.kugelfang-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-02-01 18:56                   ` Michael Buesch
2006-02-10  0:51           ` John W. Linville

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=20060201002101.GA8306@havoc.gtf.org \
    --to=jgarzik-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
    --cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
    --cc=kugelfang-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).