From: Jeff Garzik <jgarzik@pobox.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: niv@us.ibm.com, shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: Please route new work through -mm tree?
Date: Wed, 29 Sep 2004 18:30:03 -0400 [thread overview]
Message-ID: <415B376B.9090704@pobox.com> (raw)
In-Reply-To: <20040929144419.6b455343.davem@davemloft.net>
David S. Miller wrote:
> On Wed, 29 Sep 2004 17:37:47 -0400
> Jeff Garzik <jgarzik@pobox.com> wrote:
>
>
>>David S. Miller wrote:
>>
>>>When I don't have any networking work present, that tree is
>>>simply deleted. So if you pull and get a URL error, that just
>>>means no changes pending and Linus has everything. :-)
>>
>>No need to delete it. When Linus merges your stuff, net-2.6 tree
>>becomes equivalent to linux-2.6 tree.
>>
>>When you next create and push local changes, a few days later, it is
>>guaranteed that there will be no conflicts between your local and
>>bkbits.net trees.
>
>
> Ok, works for me. I'll try to do this from now on.
Cool. FWIW the only time you should need to blow away and reclone a
tree is when you reorder changesets..
Jeff
next prev parent reply other threads:[~2004-09-29 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 18:03 Please route new work through -mm tree? Stephen Hemminger
2004-09-29 18:13 ` Nivedita Singhvi
2004-09-29 18:23 ` Marcos D. Marado Torres
2004-09-29 20:22 ` David S. Miller
2004-09-29 20:58 ` Nivedita Singhvi
2004-09-29 21:24 ` David S. Miller
2004-09-29 21:37 ` Jeff Garzik
2004-09-29 21:44 ` David S. Miller
2004-09-29 22:30 ` Jeff Garzik [this message]
2004-09-29 21:12 ` Gerrit Huizenga
2004-09-29 20:19 ` David S. Miller
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=415B376B.9090704@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
--cc=shemminger@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 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.