Skip to content

Commit

Permalink
Start the move from a Sourceforge-hosted git repository to GitHub.
Browse files Browse the repository at this point in the history 
There is still more to do, grepping the source for 'sourceforge',
'sf.net', and SF will be helpful.

I tagged with 'sf_to_gh' a couple of locations that I know must be
changed, but have not been changed yet.
  • Loading branch information
@d-lamb
d-lamb committed Mar 10, 2018
1 parent 8fe8cb5 commit e189aee
Show file tree
Hide file tree
Showing 7 changed files with 70 additions and 63 deletions.
4 changes: 2 additions & 2 deletions Basic/Core/pdlcore.c.PL
View file
Expand Up @@ -1056,7 +1056,7 @@ PDL_Indx pdl_kludge_copy_$type(PDL_Indx poff, // Offset into the dest data array
/* Can't copy into a level deeper than the number of dims in the output PDL */
if(level > ndims ) {
fprintf(stderr,"pdl_kludge_copy: level=%d; ndims=%"IND_FLAG"\\n",level,ndims);
croak("Internal error - please submit a bug report at http://sourceforge.net/projects/pdl/:\\n pdl_kludge_copy: Assertion failed; ndims-1-level (%"IND_FLAG") < 0!.",ndims-1-level);
croak("Internal error - please submit a bug report at https://github.com/PDLPorters/pdl/issues:\\n pdl_kludge_copy: Assertion failed; ndims-1-level (%"IND_FLAG") < 0!.",ndims-1-level);
}
if(level >= ndims - 1) {
Expand Down Expand Up @@ -1151,7 +1151,7 @@ PDL_Indx pdl_kludge_copy_$type(PDL_Indx poff, // Offset into the dest data array

print OUT <<"!WITH!SUBS!";
default:
croak("Internal error - please submit a bug report at http://sourceforge.net/projects/pdl/:\\n pdl_kludge_copy: unknown datatype of %d.",(int)(source_pdl->datatype));
croak("Internal error - please submit a bug report at https://github.com/PDLPorters/pdl/issues:\\n pdl_kludge_copy: unknown datatype of %d.",(int)(source_pdl->datatype));
break;
}
Expand Down
55 changes: 29 additions & 26 deletions Basic/Pod/FAQ.pod
View file
Expand Up @@ -261,7 +261,7 @@ assist you in porting PDL to a new system.

PDL is available as source distribution in the
I<Comprehensive Perl Archive Network> (or CPAN) and from the
sourceforge.net project page at L<https://sourceforge.net/projects/pdl/files/>.
GitHub project page at L<https://github.com/PDLPorters/pdl>.
The CPAN archives contains not only the PDL distribution but
also just about everything else that is Perl-related. CPAN is
mirrored by dozens of sites all over the world. The main site
Expand Down Expand Up @@ -367,30 +367,35 @@ pages).

=back

If you are interested in PDL in general you can join the PDL mailing
list pdl-general@lists.sourceforge.net. This is a forum to discuss programming
issues in PDL, report bugs, seek assistance with PDL related problems,
etc. To subscribe, fill out the form at
L<http://lists.sourceforge.net/lists/listinfo/pdl-general> .

A searchable archive and a hypertext version of the traffic on this
list (1997-2004) can be found at
L<http://www.xray.mpe.mpg.de/mailing-lists/perldl/> . More recent
messages (since June 2005) can be found at TBD.
If you are interested in PDL in general you can join the pdl-general mailing
list. This is a forum to discuss programming issues in PDL, report bugs, seek
assistance with PDL related problems, etc.

If you are interested in all the technical details of the ongoing PDL
development you can join the PDL developers mailing list
pdl-devel@lists.sourceforge.net . To subscribe, fill out the form at
L<http://lists.sourceforge.net/lists/listinfo/pdl-devel> .
development you can join the pdl-devel mailing list.

Subscription and current archive links to both mailing lists can be found at

A searchable archive and a hypertext version
of the traffic on this list (1997-2004) can be found at
L<http://www.xray.mpe.mpg.de/mailing-lists/pdl-porters/> . More recent messages
(since June 2005) can be found at TBD
http://pdl.perl.org/?page=mailing-lists

Cross-posting between these lists should be avoided unless there is a
I<very> good reason for doing that.

The PDL project, begun in the late 1990s, has undergone considerable evolution
since that time, and the support for it has as well. Thus mailing-list
archives are in several places. Originally pdl-general was called 'perldl',
and pdl-devel was called 'pdl-porters'.

|Time Period | URL |
|------------|-------------------------------------------------------|
|1996 - 2004 | http://www.xray.mpe.mpg.de/mailing-lists/perldl/ |
|1997 - 2004 | http://www.xray.mpe.mpg.de/mailing-lists/pdl-porters/ |
|2005 - 2015 | perldl@jach lost??? |
|2005 - 2015 | pdl-porters@jach lost??? |

This comment has been minimized.

Sign in to view

Copy link
@mohawk2

mohawk2 Mar 10, 2018

Member

Good news, everyone! (and very nice work so far, Derek!)

http://perldl.jach.hawaii.narkive.com/
http://pdl-porters.jach.hawaii.narkive.com/
|2015 - | https://sourceforge.net/p/pdl/mailman/pdl-general/ |
|2015 - | https://sourceforge.net/p/pdl/mailman/pdl-devel/ |
|--------------------------------------------------------------------|


=head2 Q: 3.3 What is the current version of PDL ?

Expand Down Expand Up @@ -601,9 +606,9 @@ Assume you have Git installed on your system and want to download the
project source code into the directory C<PDL>. To get read-only access
to the repository, you type at the command line

git clone git://git.code.sf.net/p/pdl/code pdl-code
git clone git://github.com/PDLPorters/pdl PDL

For official PDL developers, to get read/write access to the repository
NEEDS updating (sf_to_gh): For official PDL developers, to get read/write access to the repository
type at the command line

git clone ssh://USERNAME@git.code.sf.net/p/pdl/code pdl-code
Expand All @@ -612,13 +617,11 @@ type at the command line
=head2 Q: 4.10 I had a problem with the Git version, how do I check if someone has submitted a patch?


The Sourceforge system contains a patch-manager which contains patches
that have not yet been applied to the distribution. This can be
accessed via the Tickets menu at PDL's Sourceforge project page
L<http://sourceforge.net/projects/pdl> .
The best way is to check L<https://github.com/PDLPorters/pdl/pulls> to see if
somebody has submitted a pull request related to your problem.

In addition, if you are not subscribing to the mailing list,
check the archive of the C<pdl-porters> and C<perldl> mailing lists.
check the archive of the C<pdl-devel> and C<pdl-general> mailing lists.
See L<Question 3.2|"Q: 3.2 Are there other PDL information sources on the Internet?"> for details.


Expand Down Expand Up @@ -648,7 +651,7 @@ and they won't be happy to have their recent PDL fail to build!
NOTE: git makes it very easy to maintain a separate branch of
development. [ TBD, provide information on how ].

Then update the shared repository (at SF.net) with your changes
Then update the shared repository with your changes

git push origin master

Expand Down
6 changes: 3 additions & 3 deletions Basic/SourceFilter/NiceSlice.pm
View file
Expand Up @@ -1104,12 +1104,12 @@ the bottom.
Feedback and bug reports are welcome. Please include an example
that demonstrates the problem. Log bug reports in the PDL
bug database at
issues tracker at
http://sourceforge.net/p/pdl/bugs/
https://github.com/PDLPorters/pdl/issues
or send them to the pdl-devel mailing list
E<lt>pdl-devel@lists.sourceforge.netE<gt>.
(see http://pdl.perl.org/?page=mailing-lists).
=head1 COPYRIGHT
Expand Down
41 changes: 24 additions & 17 deletions Bugs.pod
View file
Expand Up @@ -53,20 +53,14 @@ is definitely not readily searchable.

=head1 REPORTING BUGS

Please submit bug reports via the sourceforge bug tracker
interface at
Please submit bug reports via the GitHub issue tracker at

http://sourceforge.net/p/pdl/bugs/
https://github.com/PDLPorters/pdl/issues

where you can review the previously submitted bug reports.
Click on C<Create Ticket> to generate a bug report. If you do not
already have a sourceforge.net account, you will need to
get one to submit the report:

http://sourceforge.net/account/registration/

Please provide a way for the PDL developers to contact you
regarding the problem.
Click on C<New issue> to generate a bug report. If you do not
already have a GitHub account, you will need to
create one to submit the report.

Try to include any information you think might help someone
isolate, reproduce, and fix your problem.
Expand Down Expand Up @@ -129,7 +123,7 @@ A patch against the latest released version of this distribution which fixes thi

Alternatively, send an e-mail report with the above
information (including the output of C<perldl -V>)
to C<pdl-devel@lists.sourceforge.net>. See
to the pdl-devel mailing list. See

http://pdl.perl.org/?page=mailing-lists

Expand Down Expand Up @@ -159,17 +153,30 @@ L<http://pdl.perl.org> which usually gives the best results.

=head1 PATCHES

Patches can be sent to the pdl-devel mailing list
(see above) or can be directly submitted to the
patch manager
Patches can be submitted in several ways, in order of decreasing preference:

=over 4

=item 1

Fork the pdl repository on GitHub, make and test your changes, and submit a pull request;

http://sourceforge.net/p/pdl/patches/
=item 2

Edit (or suggesting an edit to) the files in-place on GitHub;

=item 3

Email a patch to the pdl-devel mailing list.

=back

Patches should be made against the latest released
PDL or, ideally, against the current git sources
which you can browse and check out at

git://git.code.sf.net/p/pdl/code
https://github.com/PDLPorters/pdl
git://github.com/PDLPorters/pdl.git

Thanks,
The PDL developers.
Expand Down
10 changes: 5 additions & 5 deletions DEVELOPMENT
View file
Expand Up @@ -5,15 +5,15 @@ not be confused with the latest public release
which will always be available from CPAN (if you
don't know what that is check the FAQ).

Public Git repository at sourceforge.net
Public Git repository
--------------------------------------------

From version PDL-2.4.4 onwards the source
distribution is in a publicly accessible Git
repository. The project is hosted at the
sourceforge site at
repository. From version PDL-2.019 onwards the
project is hosted at the GitHub site at

http://sourceforge.net/projects/pdl/
https://github.com/PDLPorters/pdl

Starting from the above URL you will find
directions on how to check out the current
Expand Down Expand Up @@ -78,7 +78,7 @@ access to the PDL Git repository.
should be able to help.)


PDL Developer Recommended Workflow:
(sf_to_gh)PDL Developer Recommended Workflow:
-----------------------------------
The actual workflow is a little more complicated. This is because
GitHub also hosts a mirror of PDL's SF repository, to enable automatic
Expand Down
6 changes: 3 additions & 3 deletions Makefile.PL
View file
Expand Up @@ -468,11 +468,11 @@ my %makefile_hash = (
'META_MERGE' => {
resources => {
homepage => 'http://pdl.perl.org/',
bugtracker => 'http://sourceforge.net/p/pdl/bugs/',
bugtracker => 'https://github.com/PDLPorters/pdl/issues',
repository => {
url => 'git://git.code.sf.net/p/pdl/code',
url => 'git://github.com/PDLPorters/pdl.git',
type => 'git',
web => 'http://sourceforge.net/p/pdl/code/ci/master/tree/',
web => 'https://github.com/PDLPorters/pdl',
},
},
no_index => { file => ['Doc/scantree.pl'] }
Expand Down
11 changes: 4 additions & 7 deletions README
View file
Expand Up @@ -82,9 +82,9 @@ basic examples of what you can do.

Bug Reports
-----------
You can check the existing PDL bugs on sourceforge at
You can check the existing PDL bugs on GitHub at

http://sourceforge.net/p/pdl/bugs/
https://github.com/PDLPorters/pdl/issues

The mailing list archives can be searched/read at

Expand All @@ -96,11 +96,8 @@ not sure what you have is a bug or not. For example, the list
is the place to go for install problems.

If you need to post a problem report, and after checking with
the perldl list that it *is* a bug, please use the sourceforge.net
tracker system following the guidance in the BUGS file:

http://sourceforge.net/p/pdl/bugs/

the pdl-general list that it *is* a bug, please use the GitHub issue
tracker system following the guidance in the BUGS file.


Notes
Expand Down

0 comments on commit e189aee

Please sign in to comment.