* nf-next-2.6.git tree updated
@ 2008-10-05 12:16 Patrick McHardy
2008-10-05 13:02 ` Patrick McHardy
0 siblings, 1 reply; 4+ messages in thread
From: Patrick McHardy @ 2008-10-05 12:16 UTC (permalink / raw)
To: Netfilter Development Mailinglist; +Cc: Pablo Neira Ayuso, Jan Engelhardt
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: nf-next-2.6.git tree updated
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
0 siblings, 1 reply; 4+ messages in thread
From: Patrick McHardy @ 2008-10-05 13:02 UTC (permalink / raw)
To: Netfilter Development Mailinglist; +Cc: Pablo Neira Ayuso, Jan Engelhardt
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: nf-next-2.6.git tree updated
2008-10-05 13:02 ` Patrick McHardy
@ 2008-10-05 13:55 ` Jan Engelhardt
2008-10-05 14:00 ` Patrick McHardy
0 siblings, 1 reply; 4+ messages in thread
From: Jan Engelhardt @ 2008-10-05 13:55 UTC (permalink / raw)
To: Patrick McHardy; +Cc: Netfilter Development Mailinglist, Pablo Neira Ayuso
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: nf-next-2.6.git tree updated
2008-10-05 13:55 ` Jan Engelhardt
@ 2008-10-05 14:00 ` Patrick McHardy
0 siblings, 0 replies; 4+ messages in thread
From: Patrick McHardy @ 2008-10-05 14:00 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: Netfilter Development Mailinglist, Pablo Neira Ayuso
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-10-05 14:00 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox