Re: git-svn aborts with "Use of uninitialized value $u" when a non-svn-backed branch is present in remote

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jun 24, 2016 at 10:06 PM, Eric Wong <e@xxxxxxxxx> wrote:
> Please don't drop Cc:, re-adding git@vger and Christian
>
> Jacob Godserv <jacobgodserv@xxxxxxxxx> 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@xxxxxxxxxxxxx
>> > 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]