On January 7, 2014 11:17:05 PM you wrote: > Am 06.01.2014 09:03, schrieb Tim E. Real: > > Hi Florian. Happy new year. > > Been coding... > > Are you getting notifications of my recent work last few days? > > I'm not even though they are turned on at github. Why? > > > > So, uh, all the README.* files and AUTHORS and ChangeLog and so on > > > > need to be moved back to the muse2 directory so that this line in the > > > > top-level CMakeLists.txt file can find them and install them: > > ## Install doc files > > file (GLOB doc_files > > > > AUTHORS > > ChangeLog > > COPYING > > NEWS > > README > > README.de > > README.effects-rack > > README.instruments > > README.ladspaguis > > README.shortcuts > > README.softsynth > > README.translate > > README.usage > > SECURITY > > ) > > > > Please do it ASAP (before next release) as the situation is not acceptable > > -> > > none of these files (except COPYING) are installed. > > > > Also it messes up my IDE - it can't see the files because the project > > > > itself really starts at /muse2, and even hand-editing the ChangeLog, > > READMEs and so on won't let the IDE commit them. > > > > So I'm not sure how to move them safely. > > > > Thanks. > > Tim. > > Hi Tim, > > the reason why at least README needs to be in ./, and not in ./muse2/, > is that GitHub automatically uses the README,COPYING etc files from the > root directory of the repository to generate a nice overview page etc. > > one might instead want to consider to eliminate the muse2 subdirectory, > and instead moving its content directly into the repo's root dir. > > however, i'm not sure how git will treat file movement when merging > branches around, we should test this beforehand. > > Cheers, > flo
Nah, I found a suitable solution: I moved all the files back into /muse2, and added a top-level file README.md README.md is a special 'markdown' (html) file which is the 'front face' of the project, an alternative to the plain README file. This file can contain LINKS to all the other (README) files. Anything we want. We just need to make it look nice, but simple. In other words, a nice html intro to MusE. Take a look at it, I just have the word 'TESTING' in there now. So the way I see it, things are just FINE, because our top-level directory is nice and clean and only contains .gitignore and README.md and /muse2. Nice and clean, uncluttered ! However, I must insist that you please do the same for your own git repo of MusE, as well as any other branches on the main repo. Or else I will do it. It is essential that these files be installed. Without them, no-one who installs MusE knows who wrote MusE, the ChangeLog, or even the LICENSE etc. This also applies to anyone who has forked the MusE git repo recently. But first let's do a nice little intro in this new top-level README.md, with links to the other READMEs, and then copy it to all the other branches. Sound good? I'm cc'ing the list so others know what's happening. Got some fairly major commits to main coming soon, maybe tonight... Thanks. Tim. ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
