could the log message be placed on top of the files in the commit?
Hi could we put the log of the commit on top before the touched files? Stef
stepharo wrote
could we put the log of the commit on top before the touched files?
+1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha ----- Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
I think it is not possible (thatâs github stuff, not ours)⦠at least it was not possible 1.5yr ago when we did it with Camilo. but I will take another look, in case things changed. Esteban
On 03 May 2015, at 04:41, Sean P. DeNigris <sean@clipperadams.com> wrote:
stepharo wrote
could we put the log of the commit on top before the touched files?
+1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha
----- Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
in fact it was also not possible discriminate the mails they sent (it was all or nothing)⦠thatâs why we receive two mails each commit, one complete unnecessary.
On 03 May 2015, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
I think it is not possible (thatâs github stuff, not ours)⦠at least it was not possible 1.5yr ago when we did it with Camilo. but I will take another look, in case things changed.
Esteban
On 03 May 2015, at 04:41, Sean P. DeNigris <sean@clipperadams.com> wrote:
stepharo wrote
could we put the log of the commit on top before the touched files?
+1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha
----- Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 03 May 2015, at 12:12, Esteban Lorenzano <estebanlm@gmail.com> wrote:
I think it is not possible (thatâs github stuff, not ours)⦠at least it was not possible 1.5yr ago when we did it with Camilo. but I will take another look, in case things changed.
I think there is a chance to do it with this magical thing: https://zapier.com <https://zapier.com/> It seems to have an email parser that is very powerful⦠so github would send there and then zappier could send a modified mail onwards (and swallow the branch one). Marcus
Esteban
On 03 May 2015, at 04:41, Sean P. DeNigris <sean@clipperadams.com> wrote:
stepharo wrote
could we put the log of the commit on top before the touched files?
+1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha
----- Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
2015-05-03 4:41 GMT+02:00 Sean P. DeNigris <sean@clipperadams.com>:
stepharo wrote
could we put the log of the commit on top before the touched files?
+1. But Nicolas wants to know if he can view the files in his favorite editor, `#(vim emacs) atRandom`ha ha
:) Sure, I can even use ed, it's only with punch cards that I feel not that confortable - lack of practice I guess. Seriously, i never read this litany of file names, that's essentially un-informative and could be removed. Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;) Nicolas
----- Cheers, Sean -- View this message in context: http://forum.world.st/could-the-log-message-be-placed-on-top-of-the-files-in... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;)
Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.
do you guys know that if you press in the link provided, for example: https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a3401... <https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a3401...> you will have all the diffs well organised and for free? Esteban ps: in fact, if possible, I wouldnât publish even the list of files changed⦠just the commit message and the link
On 03 May 2015, at 18:23, stepharo <stepharo@free.fr> wrote:
Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;)
Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.
2015-05-03 18:54 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
do you guys know that if you press in the link provided, for example:
https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a3401...
you will have all the diffs well organised and for free?
Esteban
ps: in fact, if possible, I wouldnât publish even the list of files changed⦠just the commit message and the link
Yes, message and link would be just enough. And while asking, maybe more atomic commits (single issue at a time).
On 03 May 2015, at 18:23, stepharo <stepharo@free.fr> wrote:
Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;)
Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.
2015-05-03 21:56 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice@gmail.com>:
2015-05-03 18:54 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
do you guys know that if you press in the link provided, for example:
https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a3401...
you will have all the diffs well organised and for free?
Esteban
ps: in fact, if possible, I wouldnât publish even the list of files changed⦠just the commit message and the link
Yes, message and link would be just enough. And while asking, maybe more atomic commits (single issue at a time).
Beside, non atomic commits will introduce an expressiveness bias, at least as approximated by http://redmonk.com/dberkholz/2013/03/25/programming-languages-ranked-by-expr... ;)
On 03 May 2015, at 18:23, stepharo <stepharo@free.fr> wrote:
Code diffs would be more valuable, but adopting the tools of file lovers must come with a cost ;)
Yes I would love that too. I just want to compile a list of changes automatically. May I can do in the scriptLoader instead of reparsing git.
I tried with this, but didn't know how to push it further... https://github.com/github/github-services/compare/master...bencoman:master cheers -ben On Sun, May 3, 2015 at 4:15 AM, stepharo <stepharo@free.fr> wrote:
Hi
could we put the log of the commit on top before the touched files?
Stef
On Sun, May 3, 2015 at 4:15 AM, stepharo <stepharo@free.fr> wrote:
Hi
could we put the log of the commit on top before the touched files?
Stef
On Sun, May 3, 2015 at 10:46 PM, Ben Coman <btc@openinworld.com> wrote:
I tried with this, but didn't know how to push it further... https://github.com/github/github-services/compare/master...bencoman:master
cheers -ben
Whoops. Seems I missed actually submitting a pull request for the change. Now lets see how it goes. cheers -ben
participants (6)
-
Ben Coman -
Esteban Lorenzano -
Marcus Denker -
Nicolas Cellier -
Sean P. DeNigris -
stepharo