From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: nf-next-2.6.git tree updated
Date: Sun, 05 Oct 2008 16:00:37 +0200 [thread overview]
Message-ID: <48E8C885.5020209@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0810050953300.21891@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Sunday 2008-10-05 09:02, Patrick McHardy wrote:
>> Patrick McHardy wrote:
>>> I've uploaded my current tree containing the patches applied during
>>> the netfilter workshop to kernel.org. It should show up on the public
>>> servers shortly.
>> One note - since I'm using stacked git and had to clean up a bit
>> of the history, the tree has to be recloned. Sorry about that,
>> I'll try to reduce this in the future and will add a warning in
>> case it happens.
>
> Just declare the tree as "may change anytime without notice".
> linux-next is just the same, as is my git.medozas.de/linux. As long
> as people are aware, they write their history accordingly (i.e. not
> using merge points) and hence can use rebase.
Yes, but its more complicated and I would like to provide a more
stable base since at some point patches have to be diffed against
my tree. Dave's net trees are very good at this and the extra
effort really pays of for the consumers of them.
prev parent reply other threads:[~2008-10-05 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 12:16 nf-next-2.6.git tree updated Patrick McHardy
2008-10-05 13:02 ` Patrick McHardy
2008-10-05 13:55 ` Jan Engelhardt
2008-10-05 14:00 ` Patrick McHardy [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=48E8C885.5020209@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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