incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #156: Local copy of bloodhound part of Apache repo for browse functionality
Date Mon, 27 Aug 2012 03:42:12 GMT
#156: Local copy of bloodhound part of Apache repo for browse functionality
------------------------+-----------------------
  Reporter:  gjm        |      Owner:  nobody
      Type:  task       |     Status:  new
  Priority:  critical   |  Milestone:  Release 2
 Component:  siteadmin  |    Version:
Resolution:             |   Keywords:
------------------------+-----------------------

Comment (by olemis):

 I've been thinking about doing this vs adding remote svn supported and
 spotted something that IMO is interesting to discuss . In a few words the
 fact is that if we have a local copy of ''Bloodhound'' then changeset IDs
 will not match those in ''ASF'' svn repository , because of sequential
 order. As a consequence it seems to me that default TracLinks provider
 will be hard to work with . In other scenarios (e.g. using ''hgsvn'')
 conversion tools map automatically changesets in mirror repository to
 those in source repos (e.g. by using lightweight local tags or bookmarks).
 Hence , at least in theory, in those cases it'd be possible to implement a
 custom TracLinks provider to make them point to the right web page in
 repository browser section. In this case ...

 Q:
   - Is this a real issue ?
   - If so what shall we do about that ?

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/156#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message