From: Eric Wong <e@80x24.org>
To: Jacob Godserv <jacobgodserv@gmail.com>,
Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn aborts with "Use of uninitialized value $u" when a non-svn-backed branch is present in remote
Date: Fri, 24 Jun 2016 20:06:03 +0000 [thread overview]
Message-ID: <20160624200603.GA28498@dcvr.yhbt.net> (raw)
In-Reply-To: <CALi1mtc6Byb39kbAv16vmkUVu3JDdGG4-yVrLroDVraPDxGFng@mail.gmail.com>
Please don't drop Cc:, re-adding git@vger and Christian
Jacob Godserv <jacobgodserv@gmail.com> wrote:
> > Christian (Cc-ed) also noticed the problem a few weeks ago
> > and took a more drastic approach by having git-svn die
> > instead of warning:
> > http://mid.gmane.org/1462604323-18545-1-git-send-email-chriscool@tuxfamily.org
> > which landed as commit 523a33ca17c76bee007d7394fb3930266c577c02
> > in git.git: https://bogomips.org/mirrors/git.git/patch?id=523a33ca17c7
> >
> > Is dying here too drastic and maybe warn is preferable?
>
> In my opinion this is too drastic. It keeps me from storing
> git-specific data on a git-svn mirror.
I tend to agree, but will wait to see what Christian thinks.
> Here's my setup:
> - My git-svn mirror uses git-svn to create a git repo that mirrors
> svn history. This repository is then pushed to a clean bare
> repository. So far so good. Only svn-sourced branches exist.
> - The git-svn mirror script also saves a copy of the git-svn
> configuration used to generate the git mirror repository in an
> "orphaned" branch called something like 'git-svn-conf'. This is
> completely separate from the svn history, and exists only for my
> git-svn purposes.
> - On the "client" side, another script I wrote knows how to parse the
> git-svn configuration in that 'git-svn-conf' branch to properly
> reconfigure git-svn on the local machine, so I can use 'git svn'
> themselves to commit, etc., and still generate the same hashes so
> there's no forked history during the next mirror fetch.
>
> Long story short: I have branches which aren't in SVN history for
> automated git-svn purposes.
>
> It appears that simply skipping the branch in that loop fixes the
> issue. However, I don't know how the metadata is stored and what
> exactly that loop does, so I may be creating hidden side effects I
> have been lucky enough to not trigger yet.
next prev parent reply other threads:[~2016-06-24 20:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 18:48 git-svn aborts with "Use of uninitialized value $u" when a non-svn-backed branch is present in remote Jacob Godserv
2016-06-24 14:44 ` Jacob Godserv
2016-06-24 19:35 ` Eric Wong
[not found] ` <CALi1mtc6Byb39kbAv16vmkUVu3JDdGG4-yVrLroDVraPDxGFng@mail.gmail.com>
2016-06-24 20:06 ` Eric Wong [this message]
2016-06-25 8:39 ` Christian Couder
2016-07-02 10:33 ` [PATCH] git-svn: warn instead of dying when commit data is missing Eric Wong
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160624200603.GA28498@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=jacobgodserv@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).