From: David Miller <davem@davemloft.net>
To: kaber@trash.net
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: netfilter 00/05: netfilter fixes
Date: Mon, 09 Feb 2009 16:28:29 -0800 (PST) [thread overview]
Message-ID: <20090209.162829.143182391.davem@davemloft.net> (raw)
In-Reply-To: <4990BDE6.80102@trash.net>
From: Patrick McHardy <kaber@trash.net>
Date: Tue, 10 Feb 2009 00:36:06 +0100
> My workflow is quite out of sync with modern git commands, some of
> my scripts are still adapted from bitkeeper times :)
You poor thing, I should buy you some beer :-)
But to be honest I had a caveman like mentality about
using GIT and it took me a long time to get to the
current way I do things:
1) Dark ages:
Fresh git clone, add patches, push to Linus.
Repeat, rebasing every time.
2) Brain enabled:
Stable git clone, used over and over again.
After Linus pulls, remember HEAD and use that as
base for next pull request.
Pull in Linus's tree occaisionally when conflicts
might be possible.
3) Full enlightenment:
Stable git clone, used over and over again.
Track Linus's tree using "git fetch origin"
When conflicts are possible "git pull origin"
All pull requests are sent using "origin" as
the base.
next prev parent reply other threads:[~2009-02-10 0:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:39 netfilter 00/05: netfilter fixes Patrick McHardy
2009-02-09 16:39 ` netfilter 01/05: fix tuple inversion for Node information request Patrick McHardy
2009-02-09 16:39 ` netfilter 02/05: nf_conntrack_ipv6: don't track ICMPv6 negotiation message Patrick McHardy
2009-02-09 16:39 ` netfilter 03/05: ctnetlink: allow changing NAT sequence adjustment in creation Patrick McHardy
2009-02-09 16:39 ` netfilter 04/05: ctnetlink: fix echo if not subscribed to any multicast group Patrick McHardy
2009-02-09 16:39 ` netfilter 05/05: xt_sctp: sctp chunk mapping doesn't work Patrick McHardy
2009-02-09 22:32 ` netfilter 00/05: netfilter fixes David Miller
2009-02-09 22:47 ` Patrick McHardy
2009-02-09 23:18 ` David Miller
2009-02-09 23:36 ` Patrick McHardy
2009-02-10 0:28 ` David Miller [this message]
2009-02-10 0:31 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2009-04-24 15:44 Patrick McHardy
2009-04-26 0:57 ` David Miller
2009-05-05 12:33 ` Patrick McHardy
2009-12-15 16:14 Patrick McHardy
2009-12-16 5:12 ` David Miller
2010-02-08 17:10 Patrick McHardy
2010-02-08 19:15 ` David Miller
2010-02-09 17:33 ` Patrick McHardy
2010-02-09 18:19 ` Jan Engelhardt
2010-02-10 13:52 ` Patrick McHardy
2010-02-09 20:38 ` David 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=20090209.162829.143182391.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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).