* git-svn: failure to clone logcheck's repo
@ 2007-07-13 9:36 martin f krafft
2007-07-13 9:47 ` Peter Baumann
0 siblings, 1 reply; 4+ messages in thread
From: martin f krafft @ 2007-07-13 9:36 UTC (permalink / raw)
To: git discussion list
[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]
Hi list,
I am trying to access the logcheck repository with git-svn. Even
though I can happily clone the trunk:
git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git
as soon as I try to clone the entire thing with tags and branches:
git-svn clone -T trunk -t tags -b branches
svn://svn.debian.org/svn/logcheck/logcheck git
it barfs:
Initialized empty Git repository in .git/
Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck
r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)
[...]
r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)
Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20
Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330
Following parent with do_switch
Successfully followed parent
r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)
Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029
I think I'll be fine with *not* preserving logcheck's history when
I move it to git, but thought best to let you know since this may be
a bug in git-svn.
Cheers,
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
windoze is the one-night-stand of operating systems;
you feel so cheap after having used it.
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git-svn: failure to clone logcheck's repo
2007-07-13 9:36 git-svn: failure to clone logcheck's repo martin f krafft
@ 2007-07-13 9:47 ` Peter Baumann
2007-07-13 9:56 ` Peter Baumann
2007-07-13 10:37 ` martin f krafft
0 siblings, 2 replies; 4+ messages in thread
From: Peter Baumann @ 2007-07-13 9:47 UTC (permalink / raw)
To: git discussion list
On Fri, Jul 13, 2007 at 11:36:22AM +0200, martin f krafft wrote:
> Hi list,
>
> I am trying to access the logcheck repository with git-svn. Even
> though I can happily clone the trunk:
>
> git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git
>
> as soon as I try to clone the entire thing with tags and branches:
>
> git-svn clone -T trunk -t tags -b branches
> svn://svn.debian.org/svn/logcheck/logcheck git
>
> it barfs:
>
> Initialized empty Git repository in .git/
> Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck
> r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)
> [...]
> r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)
> Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20
> Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330
> Following parent with do_switch
> Successfully followed parent
> r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)
> Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029
>
> I think I'll be fine with *not* preserving logcheck's history when
> I move it to git, but thought best to let you know since this may be
> a bug in git-svn.
>
This is a known problem. If I remember correctly,it is save to just
resume the import with git-svn fetch, and nothing bad should happen.
Just search the list archive for more info (sorry, I don't have a
reference to the thread)
-Peter
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git-svn: failure to clone logcheck's repo
2007-07-13 9:47 ` Peter Baumann
@ 2007-07-13 9:56 ` Peter Baumann
2007-07-13 10:37 ` martin f krafft
1 sibling, 0 replies; 4+ messages in thread
From: Peter Baumann @ 2007-07-13 9:56 UTC (permalink / raw)
To: git discussion list
On Fri, Jul 13, 2007 at 11:47:10AM +0200, Peter Baumann wrote:
> On Fri, Jul 13, 2007 at 11:36:22AM +0200, martin f krafft wrote:
> > Hi list,
> >
> > I am trying to access the logcheck repository with git-svn. Even
> > though I can happily clone the trunk:
> >
> > git-svn clone svn://svn.debian.org/svn/logcheck/logcheck/trunk git
> >
> > as soon as I try to clone the entire thing with tags and branches:
> >
> > git-svn clone -T trunk -t tags -b branches
> > svn://svn.debian.org/svn/logcheck/logcheck git
> >
> > it barfs:
> >
> > Initialized empty Git repository in .git/
> > Using higher level of URL: svn://svn.debian.org/svn/logcheck/logcheck => svn://svn.debian.org/svn/logcheck
> > r19 = 95d0625b6c62935cfd3e44ec7dca5b6f6b05ab44 (trunk)
> > [...]
> > r20 = a3e5240dcc4d064b46273584800d3ae7a1e21330 (trunk)
> > Found possible branch point: svn://svn.debian.org/svn/logcheck/logcheck/trunk => svn://svn.debian.org/svn/logcheck/logcheck/branches/VENDOR, 20
> > Found branch parent: (VENDOR) a3e5240dcc4d064b46273584800d3ae7a1e21330
> > Following parent with do_switch
> > Successfully followed parent
> > r21 = 0ffcb70923d77c1d24019362e1ed1cd18d05f235 (VENDOR)
> > Malformed network data: Malformed network data at /usr/local/bin/git-svn line 1029
> >
> > I think I'll be fine with *not* preserving logcheck's history when
> > I move it to git, but thought best to let you know since this may be
> > a bug in git-svn.
> >
>
> This is a known problem. If I remember correctly,it is save to just
> resume the import with git-svn fetch, and nothing bad should happen.
>
> Just search the list archive for more info (sorry, I don't have a
> reference to the thread)
Just found it. Look e.g. here on the comment from Eric Wong:
http://thread.gmane.org/gmane.comp.version-control.git/50962/focus=275913
-Peter
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git-svn: failure to clone logcheck's repo
2007-07-13 9:47 ` Peter Baumann
2007-07-13 9:56 ` Peter Baumann
@ 2007-07-13 10:37 ` martin f krafft
1 sibling, 0 replies; 4+ messages in thread
From: martin f krafft @ 2007-07-13 10:37 UTC (permalink / raw)
To: git discussion list
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
also sprach Peter Baumann <waste.manager@gmx.de> [2007.07.13.1147 +0200]:
> This is a known problem. If I remember correctly,it is save to
> just resume the import with git-svn fetch, and nothing bad should
> happen.
Yeah, this seems to work.
> Just found it. Look e.g. here on the comment from Eric Wong:
>
> http://thread.gmane.org/gmane.comp.version-control.git/50962/focus=275913
Shame on me, I really should have done the research myself. I guess
I am still too overwhelmed with git, but that won't last long,
I promise.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
spamtraps: madduck.bogus@madduck.net
"lessing was a heretics' heretic"
-- walter kaufmann
[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-07-13 10:36 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-07-13 9:36 git-svn: failure to clone logcheck's repo martin f krafft
2007-07-13 9:47 ` Peter Baumann
2007-07-13 9:56 ` Peter Baumann
2007-07-13 10:37 ` martin f krafft
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.