Re: [Jazzplusplus-user] Website documentation updates

[Pete S. <pst...@ve...>]

DM = DM
DM> I've just come from reading your last
DM> posting on devel-list
DM>
DM> This lot will hopefully get us up to date....
DM>
DM> 1. I'm posting this to jazzplusplus-user
DM> with CC to yourself.  If you already receive
DM> copies of jazzplusplus-user mail, let me know
DM> and I'll drop the CC. This will keep threads
DM> alive here.

I subscribe to, and manage, the three Jazz++ mailing lists, so you can 
drop the CC.  It wasn't true in this email, but also make sure you 
remove raw email addresses from your replies.  It feeds tjhe spam 
harvesters.  The Cygwin site maintains a list of acronyms they use in 
email posting, and in this case PCYMTNQREAIYR 
(http://cygwin.com/acronyms/#PCYMTNQREAIYR) applies ;-)

DM> 2. I'll track devel from the online archive -this
DM> will avoid list 'pollution'
DM>
DM> 3. A subversion repository of the documentation
DM> is certainly the way to go -- it keeps efforts
DM> centered around a common toolset. I can then
DM> keep my local tree synced and easily diff' out
DM> patches.

I just put the web content in the Jazz++ svn repository.  The URL is

https://jazzplusplus.svn.sourceforge.net/svnroot/jazzplusplus/web

Have at it ;-)

DM> I'm supposing I should submit patches to yourself.

Yes.  That's find for now.  Once the project grows, or if you have many 
patches, the source forge patch manager for Jazz++

http://sourceforge.net/tracker/?atid=637414&group_id=104252&func=browse

might be more appropriate.

DM> The commit should get noticed in jazzplusplus-devel

Actually it will be noticed on jazzplusplus-updates.

DM> to invite any input there. Once any patches are
DM> approved and applied to the svn repo, I'll announce
DM> same here in jazzplusplus-user, so folks know
DM> there's something new to checkout (on the website
DM> or in the code), thusly inviting folks to comment
DM> on this list as well.

Sounds good.

DM> Let me know the svn particulars once you get that
DM> end sorted, and I'll then do the same here, sanity
DM> check it etc...and we all should be happy..
DM> Well...I hope so anyhow.

The repository information is listed above.  Since you are on Linux 
boxes, use

svn diff > mypatch.patch

to generate patches and place them in the source forge patch manager or 
email them to the list.  Like I said before, if the project grows, only 
the source forge patch manager will make sense, and not the list, but 
for now, it's OK.

DM> 4. The question about 'which linux distro do I use
DM> seems to have been left hanging somehow...
DM> I was fairly sure I answered that one.  Not to worry...
DM> I've been personally building & using my own
DM> 'hand rolled' linux systems ever since I read
DM> 'The Bash to boot prompt howto' and concluding that
DM> (quote) "it looked like a fun thing to do".
DM> ...and that must've been nearly a decade ago - how
DM> time flies...
DM>
DM> There's also a couple of Debian 4.0 boxes here that
DM> I look after for other house members. I can rattle
DM> together deb packages in both 32 and 64 bit flavors
DM> if need be...whenever that time comes of course....

Kevin C. might want to comment on that.  IIRC he was interested in 
packaging and distribution; if I can ever get anything ready to distribute.

Pete