On 7/7/12, David A. Wheeler <[email protected]> wrote: > Alan Manuel Gloria <[email protected]> >> What do I git-clone? > > At this instant in time, it's: > git clone git://git.code.sf.net/p/readable/code readable-code > > However, I just requested the Allura switch, and I expect the URL to switch. > I wouldn't expect the hashes to change, but you'd have to patch the origin > URL if you git clone now.
no problem, I do this all the time at day job. > > After we switch over, I'm thinking of creating a new "lab" subdirectory, > where our experiments, eyes of newt, and plasma globes can be placed. Then, > move lots of our current code there. That way, people who just want to use > final results won't have to see the rest of things... but we can still share > experimental alternatives. Git usually handles that kind of thing pretty > well if you commit after moving (without editing the files). Why not use a stable and dev branch? Just cherry-pick-and-squash-commits between the stable and dev. You can set the current 0.2 repo to stable. At each 0.x release, cherry-pick selected dev changes and squash them into major commit changes, and then rebase dev on stable if you want (although Arne might complain, since rebasing means rewriting published dev history - still, that rebasing will get done only at 0.x public releases, so it might not be all that rough - just have a freeze date before a public release, during which time contributors won't change anything while review and cherry-picking is on-going, etc.) We can even have multiple dev branches - fork off a branch to explore some weird idea (like "." as indentation whitespace), then delete the branch if it is too weird, or merge it into the main dev branch if we decide it's actually better. Of course with multiple branches you want something like this: http://www.developerzen.com/2011/01/10/show-the-current-git-branch-in-your-command-prompt/ Arne, how good is Mercurial at handling multiple branches? How about similar "show Mercurial branch in command prompt" - does something similar exist? > > We could edit the documents in the git repo, but I'm guessing it'd be easier > to edit and share in a wiki. Do you care if the docs be in a wiki? With > the code? Somewhere else? I'd rather have stuff like e.g. my parser specs with the code (since it effectively IS code, just hand-compiled to actual Scheme). Since it's formal language you might want to restrict it a bit more, with code reviews and suchlike. Although, descriptive human-language docs can go to a wiki. You might want to wikiformat (some of) your existing pages, then redirect those URL's (302?) to wherever you intend to host the wiki. Sincerely, AmkG ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/readable-discuss
