netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Netfilter Developers <netfilter-devel@vger.kernel.org>
Subject: Re: iptables release
Date: Thu, 29 Nov 2007 21:52:00 +0100	[thread overview]
Message-ID: <474F2670.8080509@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711292044300.8275@ask.diku.dk>

Jesper Dangaard Brouer wrote:
>
> On Thu, 29 Nov 2007, Patrick McHardy wrote:
>>
>> It seems it switches the first directory and "trunk". Did you use
>> git-svnimport or just git-svn for importing?
>
> I use "git-svn":
>  git-svn clone https://svn.netfilter.org/netfilter/ -T trunk -b 
> branches -t tags
>
> And I had to update git to a newer version (1.5.3 than debians 1.4.4) 
> to make it work.
>
> Still, I don't think it got the tags and branches right, because 
> .git/refs/tags is empty. And it only gets log history back from 
> revision 3070 (thats where a "new global trunk directory" were created).
>
> When I want to sync with SVN I do:
>
>  git-checkout master
>  git-svn fetch
>  git-svn rebase
>
> To get one of my work branches up to sync I do a git rebase:
>
>  git-checkout perf_work1
>  git rebase master

Yeah, that works for importing the head and keeping in sync,
but it doesn't work for importing the entire repository with
branches and history according to the manpage. Still useful
since I hate SVN about as much as CVS :)


  reply	other threads:[~2007-11-29 20:52 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 [this message]
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=474F2670.8080509@trash.net \
    --to=kaber@trash.net \
    --cc=hawk@diku.dk \
    --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).