Re: git-svn aborts with "Use of uninitialized value $u" when a non-svn-backed branch is present in remote
- From
Christian Couder <christian.couder@gmail.com>
- Date
- Jun 25, 2016, 08:39 UTC
- Message-ID
- <CAP8UFD0+vG3i26=w7WqjYcpOLj+V6X35_W6DAiMmTpiC2kxRWA@mail.gmail.com>
- In-Reply-To
- <20160624200603.GA28498@dcvr.yhbt.net>
On Fri, Jun 24, 2016 at 10:06 PM, Eric Wong <e@80x24.org> wrote:
Show 16 quoted lines
> 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.
Yeah a warning is probably enough. Another possibility would be to default to an error that tells people about a configuration variable that could let them decide depending on their workflow if this should be an error, a warning or just be ignored.