Thanks for the info,
I'm happy to use the new httpd server that serves the help files -
that'd definitely help. My difficulty with this approach is that I'm
not sure how to get the URL -
Say for example I've done help.start(),
then I do:
help(plot)
it will redirect my web browser to the plot
Le 27/05/10 09:48, Jamie Love a écrit :
Thanks for the info,
I'm happy to use the new httpd server that serves the help files -
that'd definitely help. My difficulty with this approach is that I'm
not sure how to get the URL -
Say for example I've done help.start(),
then I do:
help(plot)
Thanks to Romain, this is perfect -
On Thu, May 27, 2010 at 8:05 PM, Romain Francois
romain.franc...@dbmail.com wrote:
Le 27/05/10 09:48, Jamie Love a écrit :
Thanks for the info,
I'm happy to use the new httpd server that serves the help files -
that'd definitely help. My difficulty with
One small technical note:
Simon said
That (non-linear history) is IMHO the biggest drawback of DVCS because
that means there is no way to link a particular build to the source
status and you cannot use globally valid build numbers.
In mercurial (Hg) a particular snapshot can be labeled with a
In mercurial (Hg) a particular snapshot can be labeled with a tag, and
then referred to by that name in the future.
Bazaar can tag revisions as well: http://wiki.bazaar.canonical.com/Tag
Git too: http://www.kernel.org/pub/software/scm/git/docs/git-tag.html
Sincerely
Sveinung Kvilhaugsvik
I think the main advantage of a DVCS is that it allows many many
people to make changes to a project and to integrate those changes in
a non-insane way. Given that R as a very restricted list of people who
actually make changes to the source, it doesn't seem that something
like git or Hg would
