I saw a trac-github integration plugin here: https://github.com/trac-hacks/trac-github
Not the same thing Douglas linked above. On Fri, Apr 26, 2019 at 6:09 PM Jeremy Huntwork < [email protected]> wrote: > On Fri, Apr 26, 2019 at 4:55 PM Bruce Dubbs <[email protected]> wrote: > > > > svn co svn://svn.linuxfromscratch.org/LFS/trunk/BOOK/ LFS > > cd LFS > > vi <file to change> > > svn diff > lfs.patch > > Send email with attachment. > > Which in Github (if you go the web editor route) can be: > > click button to fork the repo > edit file in browser > click button to submit a pull request > > A nice benefit is that I retain credit for that commit as the actual > commit author, instead of as a blurb in a comment. > > A benefit for you as the reviewer is that you don't have to locally > apply the patch and then commit it for someone else, you can just > accept the change by clicking the button if you agree. > > > > > The difference is that you need to sign up to the mailing list instead > > of the git repository. For small changes we don't even need a patch. > > Just saying what is needed is often enough. > > > > > If you haven't worked this way before, I can appreciate why you might > > > not see the advantages. To those who have done both (like me) they are > > > obvious. Even if you don't ever change LFS to git, it's worth trying > > > out collaborating this way at some point with some project. It really > > > is a much nicer way to work. > > > > I can do a git clone, but do not contribute to other projects. > > > > Actually, I think the biggest factor that makes users hesitant to > > contribute directly is that the books are written in docbook formatted > > xml. > > Yeah, that is no doubt a large factor too. > > JH > -- > http://lists.linuxfromscratch.org/listinfo/alfs-discuss > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page >
-- http://lists.linuxfromscratch.org/listinfo/alfs-discuss FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
