You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gary Martin <ga...@wandisco.com> on 2013/09/24 16:33:18 UTC
source browser active
Hi,
I would like to thank pctony for providing us with the ability to enable
our source browser interface on issues.apache.org/bloodhound - at last,
all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
valid links.
More work may be required but the initial syncing should be complete at
this point.
Cheers,
Gary
Re: source browser active
Posted by Joachim Dreimann <jo...@wandisco.com>.
On 24 September 2013 15:33, Gary Martin <ga...@wandisco.com> wrote:
> Hi,
>
> I would like to thank pctony for providing us with the ability to enable
> our source browser interface on issues.apache.org/bloodhound - at last,
> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
> valid links.
>
> More work may be required but the initial syncing should be complete at
> this point.
>
> Cheers,
> Gary
>
Excellent, thanks Gary and pctony!
--
Joachim Dreimann | *User Experience Manager*
WANdisco // *Non-Stop Data*
e. joachim.dreimann@wandisco.com
twitter @jdreimann <https://twitter.com/jdreimann>
Re: source browser active
Posted by Olemis Lang <ol...@gmail.com>.
On 9/24/13, Gary Martin <ga...@wandisco.com> wrote:
> Hi,
>
> I would like to thank pctony for providing us with the ability to enable
> our source browser interface on issues.apache.org/bloodhound - at last,
> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
> valid links.
>
> More work may be required but the initial syncing should be complete at
> this point.
>
nice !
... and jftr , there will be new styles for repository views once that
instance will be upgraded to BH>0.6
--
Regards,
Olemis - @olemislc
Re: source browser active
Posted by Gary Martin <ga...@wandisco.com>.
On 02/10/13 17:31, Olemis Lang wrote:
> On 10/2/13, Gary Martin <ga...@wandisco.com> wrote:
>> On 02/10/13 16:35, Gary Martin wrote:
>>> On 02/10/13 15:47, Olemis Lang wrote:
>>>> On 9/24/13, Gary Martin <ga...@wandisco.com> wrote:
>>>>> Hi,
>>>>>
>>>> :)
>>>>
>>>>> I would like to thank pctony for providing us with the ability to
>>>>> enable
>>>>> our source browser interface on issues.apache.org/bloodhound - at last,
>>>>> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
>>>>> valid links.
>>>>>
>>>>> More work may be required but the initial syncing should be complete at
>>>>> this point.
>>>>>
>>>> JFYI , there are a few references to changesets that are not resolved
>>>> e.g. see https://issues.apache.org/bloodhound/ticket/312#comment:8 .
>>>> Maybe this is about the commits performed during incubation phase ?
>>>>
>>> Yes, I just spotted that myself.. an obvious flaw in my idea to
>>> restrict us to the /bloodhound path.
>>>
>>> I will see if we can make it accept two directories for the one
>>> repository.
>>>
> [...]
>> Looks like that is not a current solution. There is a mention of
>> SubversionNode.get_copy_ancestry in http://trac.edgewall.org/ticket/3470
>> but at the moment I assume that this is not part of an implemented
>> solution.
>>
> I'm not aware about the details of the integration but maybe it'll be
> possible to create another repos e.g. incubator and specify a
> different path (of course , it's a sub-optimal solution but at least
> will be enough to browse old changesets ;).
>
I'll look at this again soon but I am not sure that we should be in a
rush as there may be other solutions.
Cheers,
Gary
Re: source browser active
Posted by Olemis Lang <ol...@gmail.com>.
On 10/2/13, Gary Martin <ga...@wandisco.com> wrote:
> On 02/10/13 16:35, Gary Martin wrote:
>> On 02/10/13 15:47, Olemis Lang wrote:
>>> On 9/24/13, Gary Martin <ga...@wandisco.com> wrote:
>>>> Hi,
>>>>
>>> :)
>>>
>>>> I would like to thank pctony for providing us with the ability to
>>>> enable
>>>> our source browser interface on issues.apache.org/bloodhound - at last,
>>>> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
>>>> valid links.
>>>>
>>>> More work may be required but the initial syncing should be complete at
>>>> this point.
>>>>
>>> JFYI , there are a few references to changesets that are not resolved
>>> e.g. see https://issues.apache.org/bloodhound/ticket/312#comment:8 .
>>> Maybe this is about the commits performed during incubation phase ?
>>>
>> Yes, I just spotted that myself.. an obvious flaw in my idea to
>> restrict us to the /bloodhound path.
>>
>> I will see if we can make it accept two directories for the one
>> repository.
>>
[...]
>
> Looks like that is not a current solution. There is a mention of
> SubversionNode.get_copy_ancestry in http://trac.edgewall.org/ticket/3470
> but at the moment I assume that this is not part of an implemented
> solution.
>
I'm not aware about the details of the integration but maybe it'll be
possible to create another repos e.g. incubator and specify a
different path (of course , it's a sub-optimal solution but at least
will be enough to browse old changesets ;).
--
Regards,
Olemis - @olemislc
Re: source browser active
Posted by Gary Martin <ga...@wandisco.com>.
On 02/10/13 16:35, Gary Martin wrote:
> On 02/10/13 15:47, Olemis Lang wrote:
>> On 9/24/13, Gary Martin <ga...@wandisco.com> wrote:
>>> Hi,
>>>
>> :)
>>
>>> I would like to thank pctony for providing us with the ability to
>>> enable
>>> our source browser interface on issues.apache.org/bloodhound - at last,
>>> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
>>> valid links.
>>>
>>> More work may be required but the initial syncing should be complete at
>>> this point.
>>>
>> JFYI , there are a few references to changesets that are not resolved
>> e.g. see https://issues.apache.org/bloodhound/ticket/312#comment:8 .
>> Maybe this is about the commits performed during incubation phase ?
>>
> Yes, I just spotted that myself.. an obvious flaw in my idea to
> restrict us to the /bloodhound path.
>
> I will see if we can make it accept two directories for the one
> repository.
>
> Cheers,
> Gary
Looks like that is not a current solution. There is a mention of
SubversionNode.get_copy_ancestry in http://trac.edgewall.org/ticket/3470
but at the moment I assume that this is not part of an implemented solution.
Cheers,
Gary
Re: source browser active
Posted by Gary Martin <ga...@wandisco.com>.
On 02/10/13 15:47, Olemis Lang wrote:
> On 9/24/13, Gary Martin <ga...@wandisco.com> wrote:
>> Hi,
>>
> :)
>
>> I would like to thank pctony for providing us with the ability to enable
>> our source browser interface on issues.apache.org/bloodhound - at last,
>> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
>> valid links.
>>
>> More work may be required but the initial syncing should be complete at
>> this point.
>>
> JFYI , there are a few references to changesets that are not resolved
> e.g. see https://issues.apache.org/bloodhound/ticket/312#comment:8 .
> Maybe this is about the commits performed during incubation phase ?
>
Yes, I just spotted that myself.. an obvious flaw in my idea to restrict
us to the /bloodhound path.
I will see if we can make it accept two directories for the one repository.
Cheers,
Gary
Re: source browser active
Posted by Olemis Lang <ol...@gmail.com>.
On 9/24/13, Gary Martin <ga...@wandisco.com> wrote:
> Hi,
>
:)
> I would like to thank pctony for providing us with the ability to enable
> our source browser interface on issues.apache.org/bloodhound - at last,
> all the rNNNNNNN and [NNNNNNN] links we have been putting in should be
> valid links.
>
> More work may be required but the initial syncing should be complete at
> this point.
>
JFYI , there are a few references to changesets that are not resolved
e.g. see https://issues.apache.org/bloodhound/ticket/312#comment:8 .
Maybe this is about the commits performed during incubation phase ?
--
Regards,
Olemis - @olemislc