incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Apache Flex source code - timeline for the initial code contribution
Date Wed, 04 Jan 2012 18:38:37 GMT
Yes, I understand that, but if you look in the change log and see that it is
a revert of 12345, you will not find 12345 in our code base because the
starting number looks like it is going to be much higher, and there is no
guarantee that the 12345 I referenced would match to the 12345 you look up.

Maybe we all have to remember to add some offset to the revision number for
checkins prior to some date or revision?


On 1/4/12 10:21 AM, "Douglas Arthur" <> wrote:

> As long as you're creating a true dump via "svnadmin dump", it can be loaded
> with "svnadmin load", thus preserving the history. This will not force the
> revision number to start over at 0. Revisions will continue to be able to be
> compared to previous revisions, etc...
> I'm not sure how it's handled here to migrate it, but as long as whoever
> migrates it can use "svnadmin load" there should be nothing to worry about.
> - Doug
> -----Original Message-----
> From: Alex Harui []
> Sent: Wednesday, January 04, 2012 10:55 AM
> To:
> Subject: Re: Apache Flex source code - timeline for the initial code
> contribution
> Hi Bertrand,
> It looks like we can get an svn dump.  Some questions though:
> 1) Some of our svn history contains references to revisions as in: "syncing
> rev 12345 to trunk" or "reverting 12345".  My understanding is that these
> revision numbers will no longer reference anything useful once the dump is
> imported.  How have other projects managed such a thing?
> 2) Similarly, our JIRA bugs reference svn revisions as in "fixed in rev
> 12345".  How have other project managed this?
> Thanks,
> -Alex
> On 1/4/12 9:06 AM, "Bertrand Delacretaz" <> wrote:
>> Hi,
>> On Wed, Jan 4, 2012 at 5:36 PM, Carol Frampton <> wrote:
>>> ...We're looking into preserving the history.  We're not sure yet
>>> whether or not it is feasible for us to do it.  If not maybe we can
>>> put the repository we pulled from up somewhere on adobe opensource
>>> site so the history is still available...
>> If you can get an svn dump from the existing Flex repository that
>> should work, we can ask the ASF infrastructure team to import it.
>> I'd then suggest the following process:
>> -Create the svn dump from the Adobe repository -Put it somewhere with
>> a public URL for download (as it's probably too big to attach to a
>> JIRA issue) -Submit the software grant from Adobe  [1], which includes
>> the md5 digest of the dump file -Once the grant is confirmed, create a
>> JIRA issue for the ASF infra team to import the dump
>> -Bertrand
>> [1]
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message