netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>,
	coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: iptables release
Date: Thu, 29 Nov 2007 09:27:34 +0100	[thread overview]
Message-ID: <474E77F6.8030003@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711290908240.22052@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Nov 29 2007 17:01, Yasuyuki KOZAKAI wrote:
>>> BTW, judging by your last batch of xtables patches you seem to have
>>> managed to import the netfilter SVN in git. I keep getting errors
>>> related to paths:
>>>
>>> $ git-svnimport -v -C nf.git http://svn.netfilter.org/netfilter
>>> Initialized empty Git repository in /tmp/nf.git/.git/
>>> 1: Unrecognized path: 
>>> /patch-o-matic-ng/trunk/pptp-conntrack-nat/linux/include/linux/netfilter_ipv4/ip_nat_pptp.h
>>> 1: Unrecognized path: /patch-o-matic-ng/trunk/pptp-conntrack-nat/help
>>> 1: Unrecognized path: 
>>> /patch-o-matic-ng/trunk/pptp-conntrack-nat/linux/include/linux/netfilter_ipv4/ip_conntrack_pptp.h
>>>
>>> It seems it switches the first directory and "trunk". Did you use
>>> git-svnimport or just git-svn for importing?
>> Actually, I have not succeeded to manage them. I manually do 'svn update'
>> on master branch on local git tree and commits updates, and create new branch
>> on git tree for my development.
>>
> Also, there is no indication that a move was done (e.g. r7117) but instead
> a hand copy. I prefer using native svn, or switching to git entirely.


I want to switch entirely, but first I have to manage to import the
repository :)


  reply	other threads:[~2007-11-29  8:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 16:52 iptables release Patrick McHardy
2007-11-27 18:57 ` Jan Engelhardt
2007-11-27 19:04   ` Patrick McHardy
2007-11-28 17:49     ` Jan Engelhardt
2007-11-27 21:58 ` Jesper Dangaard Brouer
2007-11-28  8:30   ` Patrick McHardy
2007-11-29  2:49 ` Yasuyuki KOZAKAI
2007-11-29  6:00   ` Yasuyuki KOZAKAI
     [not found] ` <200711290249.lAT2nkEr004081@toshiba.co.jp>
2007-11-29  7:02   ` Patrick McHardy
2007-11-29  8:01     ` Yasuyuki KOZAKAI
2007-11-29  8:10       ` Jan Engelhardt
2007-11-29  8:27         ` Patrick McHardy [this message]
2007-11-29  8:47           ` Jan Engelhardt
2007-11-29  9:07             ` Jan Engelhardt
2007-11-29  9:13               ` Patrick McHardy
2007-11-29  9:19                 ` Jan Engelhardt
2007-11-29  9:25                   ` Patrick McHardy
2007-11-29 20:46     ` Jesper Dangaard Brouer
2007-11-29 20:52       ` Patrick McHardy
2007-11-29 21:05         ` Jan Engelhardt
2007-11-29 21:37           ` Patrick McHardy
2007-11-30 17:37             ` Yasuyuki KOZAKAI
     [not found]             ` <200711301737.lAUHbXWh002545@toshiba.co.jp>
2007-11-30 17:49               ` Jan Engelhardt
2007-11-29 17:46 ` [netfilter-core] " Harald Welte
  -- strict thread matches above, loose matches on Subject: below --
2009-09-10 13:29 Patrick McHardy
2009-09-10 17:29 ` Jan Engelhardt
     [not found]   ` <4AAE7807.8050701@trash.net>
2009-09-14 17:52     ` Jan Engelhardt
2009-09-14 18:07       ` Patrick McHardy
2019-09-10 18:47 Fabio Pedretti
2019-09-11  7:33 ` Fabio Pedretti

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=474E77F6.8030003@trash.net \
    --to=kaber@trash.net \
    --cc=coreteam@netfilter.org \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=yasuyuki.kozakai@toshiba.co.jp \
    /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).