Comment 5 for bug 1815828

See https://breezy-vcs.org/developers/index.html for the developer documentation. Also happy to answer questions on IRC/the mailing list.

On 14 February 2019 17:12:03 GMT, Sunday Olutayo <email address hidden> wrote:
>Okay, it will be nice, if there is a sort of guidance or introduction,
>that will help new and potential contributors to understand the breezy
>code base.
>
>Thanks
>
>
>On 14/02/2019 5:48 PM, Jelmer Vernooij wrote:
>> That's hard to do without adding extra overhead for the non-git case
>> (importing from the other module) to the probing process.
>>
>> As indicated in the review, we should really bee end to end tests for
>> git over http.
>>
>> On 14 February 2019 12:05:25 GMT, Sunday Olutayo
><email address hidden> wrote:
>>> I just went through the changes, and I discovered that, in
>>> git/__init__.py, lines 151, 152 and 153 are doing same to lines 663,
>>> 664, 665 in git/remote.py. Is it not good to put it in a function to
>>> make future maintenance easier?
>>>
>>> Thanks
>>>
>>> --
>>> You received this bug notification because you are a bug assignee.
>>> https://bugs.launchpad.net/bugs/1815828
>>>
>>> Title:
>>> brz not working on bitbucket git repo
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/brz/+bug/1815828/+subscriptions
>>
>
>--
>You received this bug notification because you are a bug assignee.
>https://bugs.launchpad.net/bugs/1815828
>
>Title:
> brz not working on bitbucket git repo
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/brz/+bug/1815828/+subscriptions

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.