[pmwiki-users] Proposed change to pmwiki.php: Markup_e

V.Krishn vkrishn4 at gmail.com
Tue Feb 11 17:54:17 CST 2014

On Tuesday, February 11, 2014 08:47:27 PM Patrick R. Michaud wrote:
> On Tue, Feb 11, 2014 at 10:00:14AM -0500, michael paulukonis wrote:
> > How can one contribute to the code? I'm not finding it quickly on the
> > wiki [...]
> > The SVN page only discusses how to pull  the code, not to offer changes:
> > http://www.pmwiki.org/wiki/PmWiki/Subversion
> For a while I've been toying with the idea of moving PmWiki's
> source to GitHub.  It's not as simple as just converting the
> subversion repository to git, though -- we have a lot of
> packaging and build tools that rely on Subversion, and those
> would also need converting.
> Any opinions from the crowd on moving to git/GitHub?
> (There's also a tags problem in PmWiki's subversion history
> left over from the days of using CVS, and last time I did a test
> git conversion all of that had to be manually managed and
> was Not Fun.)

I have noticed some imported git project that start with some base/previous 
release and import newer ones upon it.

1. Is possible to know upto which previous version it can be imported with 
complete history and tags (i.e. no issues) ?
2. For anything prior to that version I would not mind if its single commit 
between individual version. This can be achived by simple script that 
uncompresses release archive into `git init` and committing and taging it. 
Then merging sane imported git branch upon it.
( I hope to get full history as far as 2.0.x). 


More information about the pmwiki-users mailing list