On 12/06/2019 18:24, Jeremy Huntwork wrote: > On Wed, Jun 12, 2019 at 4:55 AM Pierre Labastie <[email protected]> > wrote: >> >> On 07/06/2019 19:18, Jeremy Huntwork wrote: >>> On Sat, May 11, 2019 at 7:48 AM Pierre Labastie <[email protected]> >>> wrote: >>>> >>>> Agreed. AFAIK, Python as a good infrastructure for that. It's harder with >>>> the >>>> present XSLT/bash language! What is usually not in the docs is >>>> "instructions >>>> for use": those are the hardest to write, but we should if we want to have >>>> users :) >>> >>> >>> Can we get a repo set up for this on Github? It seems we could start >>> using pull requests like RFCs for design. >>> >> >> What do you think if we move the "pythonize" branch to master, and the master >> branch back to svn on linuxfromscratch.org? The reasons why I say this are: >> (i) I have been unable to have the github notifications be sent to this list >> (ii) I do not think anybody will help on the work I am doing on jhalfs for >> blfs. So using svn is the same for me, and at least, linuxfromscratch.org >> users can be informed of what is going on. > > That's up to you. I could probably get notifications going via a > webhook, if it's that important. However, I have to admit the last > month or so for me has also been typical: the time I have available to > help with anything is sporadic at best. I'll have on occasion free > time where I can get bursts of things done, but it isn't regular or > dependable. >
So it's done: the pythonize branch has been merged to master on github, and the master branch is back to svn on linuxfromscratch.org. Right now, not everything is functional on github, specially re. BLFS tools. But it makes a start point... I still have to set back wiki.linuxfromscratch.org to show the subversion repo in "browse source", and to update the links on the site and the wiki. -- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
