Thread: [Opalvoip-announce] Plan to move OpalVoip source repository to Git
Brought to you by:
csoutheren,
rjongbloed
Menu
▾
▴
opalvoip-announce
|
From: Craig S. <cr...@po...> - 2016-05-22 02:16:08
|
Hi all,
Robert and I are planning to migrate the Opal and PTLib code
repositories from Subversion to Git sometime in the few weeks.
The repository will stay on SourceForge, and the new repo will include
all of the history and tags so nothing should be lost.
We'd value any tips or tricks from the Opal and PTLib community. Please
email to the list or to myself or Robert.
Craig
Craig Southeren
Post Increment Consulting and Software
<mailto:cr...@po...> cr...@po...
<http://www.postincrement.com> www.postincrement.com
US: +1 415 800 4201
Mobile: +61 417231046
|
|
From: Víctor M. J. L. <vj...@ig...> - 2016-07-30 12:22:58
|
On 05/22/16 at 11:45am, Craig Southeren wrote: > Robert and I are planning to migrate the Opal and PTLib code > repositories from Subversion to Git sometime in the few weeks. Any news regarding this? Thanks vmjl |
|
From: Craig S. <cr...@po...> - 2016-07-31 11:26:40
|
Still working on it.
I’ve been unimpressed with the conversions from several of the available tools (svn2git, reposurgeon etc), so I am working on my own tool to do more sympathetic conversion.
It’s a slow process, but it’s getting there ☺
Craig
Craig Southeren
Post Increment Consulting and Software
cr...@po...
www.postincrement.com <http://www.postincrement.com/>
Mobile: +61 417231046
US: +1 415 800 4201
On 30/07/2016, 9:46 PM, "Víctor M. Jáquez L." <vj...@ig...> wrote:
On 05/22/16 at 11:45am, Craig Southeren wrote:
> Robert and I are planning to migrate the Opal and PTLib code
> repositories from Subversion to Git sometime in the few weeks.
Any news regarding this?
Thanks
vmjl
|
|
From: Sergei N. <ser...@gm...> - 2016-08-15 13:29:08
|
2016-07-31 13:55 GMT+03:00 Craig Southeren <cr...@po...>: > Still working on it. > > I’ve been unimpressed with the conversions from several of the available tools (svn2git, reposurgeon etc), so I am working on my own tool to do more sympathetic conversion. > > It’s a slow process, but it’s getting there ☺ > Hello Craig, What's wrong with existing repo on GitHub I've provided? Am I missed some patches? -- Best Regards, Sergei Nikulov |
|
From: Craig S. <cr...@po...> - 2016-08-16 02:43:08
|
There are three issues, and none of them are your fault ☺
1) There are many, many branches and tags in ptlib and Opal. The github import tool has not preserved these. Perhaps this could be fixed with a different import option?
2) Each commit has a name and email address asscociated with it. The github import tool has not associated email addresses with each commit. Maybe this is also a different import option?
3) For some of the code that was originally imported from SVN, the github import tool has created individual commits for each file. This makes the repo larger than it should be. As an example, look at the repo around the date 23 Sep 98.
The tool I am working on will address all of these issues.
Craig
Craig Southeren
Post Increment Consulting and Software
cr...@po...
www.postincrement.com <http://www.postincrement.com/>
Mobile: +61 417231046
US: +1 415 800 4201
On 15/08/2016, 6:28 AM, "Sergei Nikulov" <ser...@gm...> wrote:
2016-07-31 13:55 GMT+03:00 Craig Southeren <cr...@po...>:
> Still working on it.
>
> I’ve been unimpressed with the conversions from several of the available tools (svn2git, reposurgeon etc), so I am working on my own tool to do more sympathetic conversion.
>
> It’s a slow process, but it’s getting there ☺
>
Hello Craig,
What's wrong with existing repo on GitHub I've provided?
Am I missed some patches?
--
Best Regards,
Sergei Nikulov
|
|
From: Sergei N. <ser...@gm...> - 2016-08-16 15:13:50
|
2016-08-16 5:12 GMT+03:00 Craig Southeren <cr...@po...>: > There are three issues, and none of them are your fault ☺ > > 1) There are many, many branches and tags in ptlib and Opal. The github import tool has not preserved these. Perhaps this could be fixed with a different import option? How many? https://github.com/snikulov/opal.sf.mirror 41 branches 177 tags (releases) Is it correct? > 2) Each commit has a name and email address asscociated with it. The github import tool has not associated email addresses with each commit. Maybe this is also a different import option? >From the manual $ svn2git http://svn.example.com/path/to/repo --authors ~/authors.txt I just not use this option in my import, because I don't want to expose emails to public. > 3) For some of the code that was originally imported from SVN, the github import tool has created individual commits for each file. This makes the repo larger than it should be. As an example, look at the repo around the date 23 Sep 98. Actually, this is correct. You can ensure it by executing $ svn log -v -r {1998-09-24}:{1998-09-26} svn://svn.code.sf.net/p/opalvoip/code Second thought. Subversion was released in 2000, so initially, I suspect, you've used CVS, which work that way. > > The tool I am working on will address all of these issues. > > Craig > > Craig Southeren > Post Increment Consulting and Software > cr...@po... > www.postincrement.com <http://www.postincrement.com/> > Mobile: +61 417231046 > US: +1 415 800 4201 > > > > On 15/08/2016, 6:28 AM, "Sergei Nikulov" <ser...@gm...> wrote: > > 2016-07-31 13:55 GMT+03:00 Craig Southeren <cr...@po...>: > > Still working on it. > > > > I’ve been unimpressed with the conversions from several of the available tools (svn2git, reposurgeon etc), so I am working on my own tool to do more sympathetic conversion. > > > > It’s a slow process, but it’s getting there ☺ > > > > Hello Craig, > > What's wrong with existing repo on GitHub I've provided? > Am I missed some patches? > > -- > Best Regards, > Sergei Nikulov > > > -- Best Regards, Sergei Nikulov |
|
From: Craig S. <cr...@po...> - 2016-08-16 16:04:49
|
I was looking at the wrong GitHub repo. You have two Ptlib mirrors - one with branches, one without :) The email addresses should be in the repo- they are already public in the subversion, yes ? I agree the revisions are there in the subversion repo, but I want them cleaned up anyway to make the repo cleaner Craig Sent from my iPhone > On 16 Aug 2016, at 8:13 AM, Sergei Nikulov <ser...@gm...> wrote: > > 2016-08-16 5:12 GMT+03:00 Craig Southeren <cr...@po...>: >> There are three issues, and none of them are your fault ☺ >> >> 1) There are many, many branches and tags in ptlib and Opal. The github import tool has not preserved these. Perhaps this could be fixed with a different import option? > > How many? > https://github.com/snikulov/opal.sf.mirror > 41 branches > 177 tags (releases) > > Is it correct? > >> 2) Each commit has a name and email address asscociated with it. The github import tool has not associated email addresses with each commit. Maybe this is also a different import option? > > From the manual > $ svn2git http://svn.example.com/path/to/repo --authors ~/authors.txt > > I just not use this option in my import, because I don't want to > expose emails to public. > >> 3) For some of the code that was originally imported from SVN, the github import tool has created individual commits for each file. This makes the repo larger than it should be. As an example, look at the repo around the date 23 Sep 98. > > Actually, this is correct. You can ensure it by executing > $ svn log -v -r {1998-09-24}:{1998-09-26} svn://svn.code.sf.net/p/opalvoip/code > > Second thought. > Subversion was released in 2000, so initially, I suspect, you've used > CVS, which work that way. > >> >> The tool I am working on will address all of these issues. >> >> Craig >> >> Craig Southeren >> Post Increment Consulting and Software >> cr...@po... >> www.postincrement.com <http://www.postincrement.com/> >> Mobile: +61 417231046 >> US: +1 415 800 4201 >> >> >> >> On 15/08/2016, 6:28 AM, "Sergei Nikulov" <ser...@gm...> wrote: >> >> 2016-07-31 13:55 GMT+03:00 Craig Southeren <cr...@po...>: >>> Still working on it. >>> >>> I’ve been unimpressed with the conversions from several of the available tools (svn2git, reposurgeon etc), so I am working on my own tool to do more sympathetic conversion. >>> >>> It’s a slow process, but it’s getting there ☺ >> >> Hello Craig, >> >> What's wrong with existing repo on GitHub I've provided? >> Am I missed some patches? >> >> -- >> Best Regards, >> Sergei Nikulov > > > > -- > Best Regards, > Sergei Nikulov |
|
From: Sergei N. <ser...@gm...> - 2016-08-16 16:26:07
|
2016-08-16 19:04 GMT+03:00 Craig Southeren <cr...@po...>: > I was looking at the wrong GitHub repo. You have two Ptlib mirrors - one with branches, one without :) > > The email addresses should be in the repo- they are already public in the subversion, yes ? Anyway, this is possible. Could you please check README here https://github.com/nirvdrum/svn2git ? It shows how to export authors.txt file from subversion. > I agree the revisions are there in the subversion repo, but I want them cleaned up anyway to make the repo cleaner It is also possible, by removing old (pre-svn revisions) unless you want to keep full history. Then use it as is. option --revision <<starting_revision_number>> should help by starting from upper svn revisions. > > Craig > > Sent from my iPhone > >> On 16 Aug 2016, at 8:13 AM, Sergei Nikulov <ser...@gm...> wrote: >> >> 2016-08-16 5:12 GMT+03:00 Craig Southeren <cr...@po...>: >>> There are three issues, and none of them are your fault ☺ >>> >>> 1) There are many, many branches and tags in ptlib and Opal. The github import tool has not preserved these. Perhaps this could be fixed with a different import option? >> >> How many? >> https://github.com/snikulov/opal.sf.mirror >> 41 branches >> 177 tags (releases) >> >> Is it correct? >> >>> 2) Each commit has a name and email address asscociated with it. The github import tool has not associated email addresses with each commit. Maybe this is also a different import option? >> >> From the manual >> $ svn2git http://svn.example.com/path/to/repo --authors ~/authors.txt >> >> I just not use this option in my import, because I don't want to >> expose emails to public. >> >>> 3) For some of the code that was originally imported from SVN, the github import tool has created individual commits for each file. This makes the repo larger than it should be. As an example, look at the repo around the date 23 Sep 98. >> >> Actually, this is correct. You can ensure it by executing >> $ svn log -v -r {1998-09-24}:{1998-09-26} svn://svn.code.sf.net/p/opalvoip/code >> >> Second thought. >> Subversion was released in 2000, so initially, I suspect, you've used >> CVS, which work that way. >> >>> >>> The tool I am working on will address all of these issues. >>> >>> Craig >>> >>> Craig Southeren >>> Post Increment Consulting and Software >>> cr...@po... >>> www.postincrement.com <http://www.postincrement.com/> >>> Mobile: +61 417231046 >>> US: +1 415 800 4201 >>> >>> >>> >>> On 15/08/2016, 6:28 AM, "Sergei Nikulov" <ser...@gm...> wrote: >>> >>> 2016-07-31 13:55 GMT+03:00 Craig Southeren <cr...@po...>: >>>> Still working on it. >>>> >>>> I’ve been unimpressed with the conversions from several of the available tools (svn2git, reposurgeon etc), so I am working on my own tool to do more sympathetic conversion. >>>> >>>> It’s a slow process, but it’s getting there ☺ >>> >>> Hello Craig, >>> >>> What's wrong with existing repo on GitHub I've provided? >>> Am I missed some patches? >>> >>> -- >>> Best Regards, >>> Sergei Nikulov >> >> >> >> -- >> Best Regards, >> Sergei Nikulov -- Best Regards, Sergei Nikulov |
Thanks for helping keep SourceForge clean.
X