netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@computergmbh.de>
To: Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>
Cc: kaber@trash.net, hawk@diku.dk, netfilter-devel@vger.kernel.org
Subject: Re: iptables release
Date: Fri, 30 Nov 2007 18:49:48 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711301846491.18767@fbirervta.pbzchgretzou.qr> (raw)
In-Reply-To: <200711301737.lAUHbXWh002545@toshiba.co.jp>


On Dec 1 2007 02:37, Yasuyuki KOZAKAI wrote:
>
>$ svn log -r5092 -v http://svn.netfilter.org/netfilter
>------------------------------------------------------------------------
>r5092 | (no author) | 2004-10-11 22:40:52 +0900 (Mon, 11 Oct 2004) | 1 line
>
>This is an empty revision for padding.

While empty commits can happen (it does take a specific course of action
though), the log message is unusual, esp. with (no author) and "This is an
empty revision for padding".

>------------------------------------------------------------------------
>
>** What I did to create iptables git tree
>
>I did
>	$ git-svnimport -v -s 702 -l 3070 -T iptables/trunk	\
>		http://svn.netfilter.org/netfilter 
>
>I thought that such argument to -T was not expected by the author of
>git-svnimport, but it seemd to work. ;) I did not use -b and -t for
>branches and tags. Because I found that some commits on 'origin' were
>broken by them.
>
>Sometimes the TCP connection to SVN server was disconnected while importing.
>In that case, I reset 'origin' and 'master' branch so that they refered
>the last suceeded commit, removed .git/SVN2GIT_HEAD and .git/ORIG_HEAD,
>and excecuted git-svnimport without '-s' again.

I would have rsynced the svn tree off, then do a local svn-to-git transform.
That would have avoided potentially dangerous disconnects.

>** A Comment
>Well, I don't want to do this again :)

Heh.

  parent reply	other threads:[~2007-11-30 17:49 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
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 [this message]
2007-11-29 17:46 ` [netfilter-core] " Harald Welte
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=Pine.LNX.4.64.0711301846491.18767@fbirervta.pbzchgretzou.qr \
    --to=jengelh@computergmbh.de \
    --cc=hawk@diku.dk \
    --cc=kaber@trash.net \
    --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).