On 01.07.21 04:17, Waldek Hebisch wrote:
> On Wed, Jun 30, 2021 at 03:25:52PM +0200, Ralf Hemmecke wrote:
>> Where are the diffs to install.rst and INSTALL.sh from wip/rstdoc?
>>
https://github.com/fricas/fricas/pull/56
> They were attached to my previous mail.
Oops. Thanks.
>> I thought you would consider the wip/rstdoc before the release. Now the
>> documentation for 1.3.7 is as it is --- out of date.
>
> Sorry. You wrote about update to
https://fricas.github.io, it
> was not clear if that affects anything going into release
> tarball. In fact together with branch it suggested opposite.
Why? A branch only says that it is work that is developed (more or less)
independently from the mainline and can be accessed publicly by others.
I called it "wip", because it is work-in-progress. That wip says that
one might expect that I will freely rebase that branch to any other
place, i.e. just "git pull" will not usually work, but one must rather
use "git fetch" and then sort out the stuff on his/her local repository.
> More generally many thing (most unrelated to FriCAS) take
> me now more time than in the past. In case of FriCAS
> Github (at least now) means that things take more time.
Probably depends on how you work.
> In particular to review code I need a diff, and
> ATM I have problems getting them from Github.
That is strange. Github shows you the branch where the commit is on, for
example for my wip/rstdoc branch, it lives on my github repo.
In particular you can easily few the commits via
https://github.com/hemmecke/fricas/commits/wip/rstdoc
Clicking through you see that you only need the git-hash of the commit
and append a ".patch" to it in order to get it as plain text.
https://github.com/hemmecke/fricas/commit/2ced98ab782b62070ca27549daf9574352c65bd6.patch
This is a bit more difficult, if there is a series of commits that must
be considered.
Or you simply use the power of a DVCS. Connect your *local* repo to my
github repo via
git remote add hemmecke
https://github.com/hemmecke/fricas.git
You only have to do this once. Then it is a simple
git fetch hemmecke
git show hemmecke/wip/rstdoc
And if you want the previous commit, then append a ^ (caret) to the name
that specifies the commit. OK I stop teaching you git (erm, helping you
with git), but there are a number of quite useful git commands that are
not so obvious when one just browses through the git documentation. For
example, "git stash" and "git stash pop" is a wonderful gem.
> Also, Github generates a lot of noise and simply
> it is easy to overlook important thing in the noise.
True. But last time you wrote to fricas-devel to ask whether someone
still has issues that should be solveve before a release.
> Given lack of time I had to limit things to those that
> I can do quickly. Now, in my opinion getting out the
> release was important. There are several known problems
> that that we would like to fix, but were not fixed.
> Still, there are important fixes and new code.
"*we* would like to fix"? Why do you write "we" when you do almost
everything yourself. A bit more community involvment wouldn't be a bad
thing, no?
Ralf