From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Cc: Netdev List <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] 2.6.x more net driver updates
Date: Mon, 27 Jun 2005 08:44:06 -0400 [thread overview]
Message-ID: <42BFF496.3040105@pobox.com> (raw)
In-Reply-To: <42BFEF86.8090000@pobox.com>
Jeff Garzik wrote:
> Please pull from the 'upstream' branch of
> rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
>
> to obtain the various changes described in the attachment.
Or, if you wanted to be experimental, you could pull tag (not branch)
'upstream-20050627-1' of
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
to obtain the same changes.
I think I will start using tags for my submissions, which will eliminate
an old problem with BK: After emailing a BitKeeper pull request to you,
I had to stop pushing to the repo, until you pulled. With tags, I can
keep on committing changes, without worrying that you are pulling from a
moving target.
Jeff
parent reply other threads:[~2005-06-27 12:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <42BFEF86.8090000@pobox.com>]
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=42BFF496.3040105@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).