"Not that" should be "Note that" On Mon, May 1, 2017 at 3:22 PM, Bill Deegan <[email protected]> wrote:
> Wiki page to fill in > > https://bitbucket.org/scons/scons/wiki/D%20Language%20Support > > Not that multiple heads named via book marks is mercurial's answer to > transiant branches. > Not as simple as git, but not too painful once you get the hang of it. > (It's in the wiki page on mercurial workflows I sent) > > -Bill > > On Mon, May 1, 2017 at 2:45 PM, Russel Winder <[email protected]> > wrote: > >> On Mon, 2017-05-01 at 11:29 -0400, Bill Deegan wrote: >> > Russel, >> > >> > There's a wiki page on mercurial workflows with info answering >> > exactly your >> > question. >> > https://bitbucket.org/scons/scons/wiki/DeveloperGuide/MercurialWorkfl >> > ows#markdown-header-working-on-several-branches-at-once >> >> I'll follow that up. The lack of transient feature branches (as in Git) >> in Mercurial is beginning to p@@s me off. >> >> > Here's a page for you to fill out. >> > I'll figure out where to link to it from a bit later. >> >> I suspect I am missing the URL of the page to complete. Sorry I haven't >> done wikis for over a decade. >> >> > I'm tempted to push the wiki content into the website. >> > I'm not sure the wiki's getting indexed by google.. >> >> I would argue that a wiki is a system for when the rest of the stuff is >> in a centralised VCS with no non-committer merging. Given the world of >> DVCS, wikis are essentially redundant: with DVCS anyone can propose a >> pull request to make a change. The downside is that wikis have a >> source/WYSIWYG editing, whereas pull requests are source only. >> >> If Google is not indexing the wiki we do have to perturb the system. >> >> -- >> Russel. >> ============================================================ >> ================= >> Dr Russel Winder t: +44 20 7585 2200 voip: >> sip:[email protected] >> 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] >> London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder >> >> _______________________________________________ >> Scons-dev mailing list >> [email protected] >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> >> >
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
