the mail is not made for version control, github is. Why you would prefer a
static way of doing things, from a very dynamic website ?

When you commit to a github repo everyone that watches that repo , that is
everyone that is either a contributor to that repo or a github user that
has clicked the watch button will be alerted about everything related to
that repo. The alerts appear in the front page of github.com when you log
in. That includes commits, pull requests, new branches, issues, bugs,
feature requests you name it. You could link that feed to your email so you
get email alerts but personally I prefer keeping my email seperate from
version controlling stuff.

The advantages of github are too numerous to go in detail here, just read
the github documentation. But to be put short, its easy to link towards
other commits, you can comment commits , you can even comment specific
lines of code (even using markdown ),  and edit and commit on the fly using
the website without opening pharo or git pulling to your local repo.
Personally I would prefer to see a lot more pull requests because they are
a very nice way to chain commits together and view them as one entity since
they will concern the same matter. Pull requests also can be chained to
issues and bug reports to mark the closed or open.

What you list you refer to ? The link
https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a8bab3c28e673114c,
refers to a single commit with a ton of renamed files. You mean how you can
get the list with the diff of each file changed ? thats easy, click on the
commit. If you go to the repo for example here
https://github.com/pharo-project/pharo-core/commits/4.0 clicking .... will
expand the commit message but you if click on the commit itself will send
you to the list of the diff log for that commit. Do you mean something else
?



On Sat, Sep 5, 2015 at 10:02 AM stepharo <[email protected]> wrote:

> Hi
>
> I still think that I would like in the squeak mailing-list to see the
> diff of every commit by mail.
> How can we enable that? Marcus you complain that not enough people are
> active but we do not engage people by showing
> changes. oh yes they can - by reading git commit.... oh boy if we
> believe that people systematically have a look at that then
> we are pretty naive.
>
> Now do not tell me that I can browse git commit I know it and this is
> not what I need.
> I need SYSTEMATIC awareness of a change. I NEED everybody to be able to
> have look before deleting a mail.
> It is working in Squeak. I can in my mail look at the changes.
>
> Or of course nobody cares in Pharo about changes and we can get regression.
>
> Another question: how can I get the list of links to git with the commit
> logs like
>
> https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a8bab3c28e673114c
> below?
> How can I get the list? so that I can browse (I'm probably one of the
> two few interested in fixing bugs after they got introduced).
>
>
> Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core
> Commit: 8a1f79b44b14f8eafaf6d91a8bab3c28e673114c
>
> https://github.com/pharo-project/pharo-core/commit/8a1f79b44b14f8eafaf6d91a8bab3c28e673114c
>
> Author: Jenkins Build Server <[email protected]> Date: 2015-09-04
> (Fri, 04 Sep 2015)
>
>

Reply via email to