Hi guys, Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day? Also why canât I access anything else when Komitter window is open? Uko
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain. We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P Ben On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
I am actually using it since 2 days. Cool work! Cheers, R On Dec 4, 2013, at 2:42 PM, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P
The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain. We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P
Ben
On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P
The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain.
Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window. Uko
We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P
Ben
On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
I will give a try later today :P Ben On 04 Dec 2013, at 14:47, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P
The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain.
Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window.
Uko
We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P
Ben
On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
Thanks once more for your effort. This is a really important tool for me. Uko On 04 Dec 2013, at 14:52, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I will give a try later today :P
Ben
On 04 Dec 2013, at 14:47, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P
The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain.
Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window.
Uko
We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P
Ben
On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
Does Kommitter enables partial commits (cherry picking) for a package? If so, my question is how does it deal with MC ancestry? Imagine I have a package- A.247 from my-trunk. I merge some A.312 from my-work repository with work in progress. Now I want to cherry pick the changes which are OK, and publish only those to my-trunk. I do so in my-trunk/A.313. Will A.312 be in the ancestry of A.313? Logically as MC is working, yes, because it is in the ancestry of in-image working copy. What if I later download A.313 from my-trunk in a fresh image and try to merge A.312 to finish the work in progress? IMO, this is not possible, A312 being an ancestor, no change will happen. So, it sounds like when I committed my-trunk/A.313 with partial changes, I should have commited my-work/A.314 immediately after with the rest of pending changes... If I forgot to do so and threw my image away, from a fresh image, it is still possible to load A.312, merge A.313, and publish A.314 in my-work repo. But then it rather complicates the flow... If we commit/merge carelessly, we might throw away some valuable work in progress. The fear of such scenario prevented us to integrate a change from Bert in Squeak/trunk enabling such partial commits (directly from MC UI in Squeak case). 2013/12/4 Stéphane Ducasse <stephane.ducasse@inria.fr>
+1
Thanks once more for your effort. This is a really important tool for me.
Uko
Err, from a fresh image, we should not merge A.313 but adopt it in our ancestry, else merging will remove all the pending changes... 2013/12/4 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com>
Does Kommitter enables partial commits (cherry picking) for a package? If so, my question is how does it deal with MC ancestry?
Imagine I have a package- A.247 from my-trunk. I merge some A.312 from my-work repository with work in progress. Now I want to cherry pick the changes which are OK, and publish only those to my-trunk. I do so in my-trunk/A.313. Will A.312 be in the ancestry of A.313? Logically as MC is working, yes, because it is in the ancestry of in-image working copy.
What if I later download A.313 from my-trunk in a fresh image and try to merge A.312 to finish the work in progress? IMO, this is not possible, A312 being an ancestor, no change will happen.
So, it sounds like when I committed my-trunk/A.313 with partial changes, I should have commited my-work/A.314 immediately after with the rest of pending changes... If I forgot to do so and threw my image away, from a fresh image, it is still possible to load A.312, merge A.313, and publish A.314 in my-work repo.
But then it rather complicates the flow... If we commit/merge carelessly, we might throw away some valuable work in progress. The fear of such scenario prevented us to integrate a change from Bert in Squeak/trunk enabling such partial commits (directly from MC UI in Squeak case).
2013/12/4 Stéphane Ducasse <stephane.ducasse@inria.fr>
+1
Thanks once more for your effort. This is a really important tool for me.
Uko
Nicolas
From what I understand Kommitter just filters the entities that will be passed as modified and as such does not change the ancestry of a package.
Stef On Dec 4, 2013, at 8:12 PM, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Does Kommitter enables partial commits (cherry picking) for a package? If so, my question is how does it deal with MC ancestry?
Imagine I have a package- A.247 from my-trunk. I merge some A.312 from my-work repository with work in progress. Now I want to cherry pick the changes which are OK, and publish only those to my-trunk. I do so in my-trunk/A.313. Will A.312 be in the ancestry of A.313? Logically as MC is working, yes, because it is in the ancestry of in-image working copy.
What if I later download A.313 from my-trunk in a fresh image and try to merge A.312 to finish the work in progress? IMO, this is not possible, A312 being an ancestor, no change will happen.
So, it sounds like when I committed my-trunk/A.313 with partial changes, I should have commited my-work/A.314 immediately after with the rest of pending changes... If I forgot to do so and threw my image away, from a fresh image, it is still possible to load A.312, merge A.313, and publish A.314 in my-work repo.
But then it rather complicates the flow... If we commit/merge carelessly, we might throw away some valuable work in progress. The fear of such scenario prevented us to integrate a change from Bert in Squeak/trunk enabling such partial commits (directly from MC UI in Squeak case).
2013/12/4 Stéphane Ducasse <stephane.ducasse@inria.fr> +1
Thanks once more for your effort. This is a really important tool for me.
Uko
On 04 Dec 2013, at 20:12, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Does Kommitter enables partial commits (cherry picking) for a package? If so, my question is how does it deal with MC ancestry?
Imagine I have a package- A.247 from my-trunk. I merge some A.312 from my-work repository with work in progress. Now I want to cherry pick the changes which are OK, and publish only those to my-trunk. I do so in my-trunk/A.313. Will A.312 be in the ancestry of A.313? Logically as MC is working, yes, because it is in the ancestry of in-image working copy.
What if I later download A.313 from my-trunk in a fresh image and try to merge A.312 to finish the work in progress? IMO, this is not possible, A312 being an ancestor, no change will happen.
This is indeed what is happening. A solution would be to allow to merge with an ancestor. After some investigation, itâs doable. The âproblemâ is I do not know how to detect that a version has been âfully-merged" already or not. But with the patch is juste made, you can merge with your ancestors. Another approach would be the git one. When you merge, you commit automatically the merge. Ben
So, it sounds like when I committed my-trunk/A.313 with partial changes, I should have commited my-work/A.314 immediately after with the rest of pending changes... If I forgot to do so and threw my image away, from a fresh image, it is still possible to load A.312, merge A.313, and publish A.314 in my-work repo.
But then it rather complicates the flow... If we commit/merge carelessly, we might throw away some valuable work in progress. The fear of such scenario prevented us to integrate a change from Bert in Squeak/trunk enabling such partial commits (directly from MC UI in Squeak case).
2013/12/4 Stéphane Ducasse <stephane.ducasse@inria.fr> +1
Thanks once more for your effort. This is a really important tool for me.
Uko
On Wed, Dec 4, 2013 at 2:47 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P
The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain.
Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window.
I was thinking on that too, yep :)
Uko
We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P
Ben
On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
On 04 Dec 2013, at 14:56, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On Wed, Dec 4, 2013 at 2:47 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo@gmail.com> wrote:
I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) the repository problem is an issue with the credentials. The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P
The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain.
Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window.
I was thinking on that too, yep :)
SourceTree works like that and none complains. Of course it has some auto-refresh, but we can survive without that. Uko
Uko
We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P
Ben
On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
Hi, I think that you need firstly to open Monticello and add your user name and password to the Pharo Inbox repository settings. -- Pavel 2013/12/4 Yuriy Tymchuk <yuriy.tymchuk@me.com>
Hi guys,
Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day?
Also why canât I access anything else when Komitter window is open?
Uko
participants (7)
-
Benjamin -
Esteban Lorenzano -
Nicolas Cellier -
Pavel Krivanek -
Roberto Minelli -
Stéphane Ducasse -
Yuriy Tymchuk