- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 17348 Enhance shortcut learnability

by Cyril Ferlicot D.

Le 12/01/2016 21:03, Henrik Nergaard a Ã©crit : > Hi Stef, > > > > Something like this? (see attachment) > > > > Best regards, > > Henrik > > Hi, I think it would be cool to also have a setting to get it with an #inform: instead of a full Morph. I would like to get a reminder of the shortcuts but not in all my screen. A little popup at the bottom left is less invasive. So I think that we should be able to get both. What do you think ? -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Cyril Ferlicot D.

Le 13/01/2016 16:36, stepharo a Ã©crit : > So what is the conclusion? > Can anybody get the launcher open both prespur and spur images? > > Stef > > > Since more than one week I can on Windows and Linux :) -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 13, 2016

Sounds like Goodies

by Torsten Bergmann

The dolphin 7 open source repo includes some contributions from Udo including an implementation for Levenshtein distance [1]. It's a single method + test case and easy to port. The algorithm [2] is useful to find out how close two strings are (approximate string matching). There is also SoundEx [4] and SoundsLike [5] (Soundex, Double Metaphone and NYSIIS algorithms) for Pharo available. I just want to let anyone know - just in case someone works on a more "robust" autocompletion that is also typo aware. ;) Having custom templates [6] like in Eclipse would also be good to have in future Pharo code editor. More to add to the wishlist? Damn ... Santa already passed by... Have fun T. [1] https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneid… [2] https://en.wikipedia.org/wiki/Levenshtein_distance [3] https://github.com/dolphinsmalltalk/Contributions/tree/master/Udo%20Schneid… [4] http://smalltalkhub.com/#!/~riverdusty/SXSoundEx [5] http://www.smalltalkhub.com/#!/~UdoSchneider/SoundsLike [6] http://www.tutorialspoint.com/eclipse/eclipse_code_templates.htm

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Blondeau Vincent

> -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > stepharo > EnvoyÃ© : mercredi 13 janvier 2016 16:37 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] How to get launcher launching Spur images? > > So what is the conclusion? > Can anybody get the launcher open both prespur and spur images? I can. You can try the latest version. It should work. Vincent > > Stef > > > Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : > > I confirm it works under W7 with Spur and not spur images. > > Thanks ! > > > > I think https://github.com/pharo-project/pharo-launcher/issues/1 can be > closed now? > > > > Vincent > > > >> -----Message d'origine----- > >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part > >> de Stephan Eggermont EnvoyÃ© : mercredi 13 janvier 2016 12:35 Ã : > >> pharo-dev(a)lists.pharo.org Objet : Re: [Pharo-dev] How to get launcher > >> launching Spur images? > >> > >> On 13-01-16 12:25, Blondeau Vincent wrote: > >>> Under Windows, this cmd is working: > >>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. > >>> Does it work under Mac (with real double quotes and not 2 single > quotes)? > >>> If no, we should do something that is platform dependent.. > >> Yes, it works. Please confirm if version 87 works for you > >> > >> Stephan > >> > >> > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout virus, > l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne > saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its integrity > cannot be secured on the Internet, the Worldline liability cannot be triggered > for the message content. Although the sender endeavours to maintain a > computer virus-free network, the sender does not warrant that this > transmission is virus-free and will not be liable for any damages resulting > from any virus transmitted. > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by Serge Stinckwich

At the moment, I have 2 Pharo Launcher one for pre-Spur images and another one for Spur images ... On Wed, Jan 13, 2016 at 4:36 PM, stepharo <stepharo(a)free.fr> wrote: > So what is the conclusion? > Can anybody get the launcher open both prespur and spur images? > > Stef > > > Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : > >> I confirm it works under W7 with Spur and not spur images. >> Thanks ! >> >> I think https://github.com/pharo-project/pharo-launcher/issues/1 can be >> closed now? >> >> Vincent >> >>> -----Message d'origine----- >>> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >>> Stephan Eggermont >>> EnvoyÃ© : mercredi 13 janvier 2016 12:35 >>> Ã : pharo-dev(a)lists.pharo.org >>> Objet : Re: [Pharo-dev] How to get launcher launching Spur images? >>> >>> On 13-01-16 12:25, Blondeau Vincent wrote: >>>> >>>> Under Windows, this cmd is working: >>>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. >>>> Does it work under Mac (with real double quotes and not 2 single >>>> quotes)? >>>> If no, we should do something that is platform dependent.. >>> >>> Yes, it works. Please confirm if version 87 works for you >>> >>> Stephan >>> >>> >> >> >> Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage >> exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret >> professionnel. Si vous recevez ce message par erreur, merci d'en avertir >> immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne >> pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra >> Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs >> efforts soient faits pour maintenir cette transmission exempte de tout >> virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa >> responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un >> virus transmis. >> >> This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As its >> integrity cannot be secured on the Internet, the Worldline liability cannot >> be triggered for the message content. Although the sender endeavours to >> maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted. > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 13, 2016

Re: [Pharo-dev] 17348 Enhance shortcut learnability

by stepharo

Sweet! I was thinking to put it below and smaller but this is cool. Stef Le 12/1/16 21:03, Henrik Nergaard a Ã©crit : > > Hi Stef, > > Something like this? (see attachment) > > Best regards, > > Henrik > > *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On Behalf > Of *stepharo > *Sent:* Monday, January 11, 2016 4:52 PM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > *Subject:* Re: [Pharo-dev] 17348 Enhance shortcut learnability > > Henrik > > Thanks. What I would love to get is > > another little morph below the shortcut with the name of the menu > like that we can learn that the tools xxx is launched with > shortcut cmd X > > I think that we should have a preference that does not flush the > counters at startup > > Stef > > Le 11/1/16 12:14, Henrik Nergaard a Ã©crit : > > Somehow it integrated > > ______________ > > Name: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.2 > > Author: tr > > Time: 8 January 2016, 4:18:55.135106 pm > > UUID: 0aa30f76-84f3-0449-acde-172e56ea3615 > > Ancestors: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.1 > > Dependencies: Morphic-Base-tr.526 > > better version > > instead of: > > ____________ > > Name: SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.2 > > Author: HenrikNergaard > > Time: 8 January 2016, 11:01:18.490743 pm > > UUID: 2a6f1c3f-a0b3-524d-9095-02fb42ab8358 > > Ancestors: SLICE-Issue-17348-Enhance-shortcut-learnability-tr.1 > > Dependencies: Morphic-Base-HenrikNergaard.526 > > Refactor of initial code. > > I have updated and merged a new slice (in Image 50521) which > should fix it. The correct version that should be integrated is: > > Name: SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.5 > > Author: HenrikNergaard > > Time: 11 January 2016, 12:17:08.504781 am > > UUID: f0271c17-07a7-0d4e-a6eb-d2fef9b2853c > > Ancestors: > SLICE-Issue-17348-Enhance-shortcut-learnability-HenrikNergaard.4 > > Dependencies: Morphic-Base-HenrikNergaard.530 > > remove unused variable. > > Best regards, > > Henrik > > *From:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *On > Behalf Of *Marcus Denker > *Sent:* Monday, January 11, 2016 11:35 AM > *To:* Pharo Development List <pharo-dev(a)lists.pharo.org> > <mailto:pharo-dev@lists.pharo.org> > *Subject:* Re: [Pharo-dev] 17348 Enhance shortcut learnability > > Hello, > > I wil reopen the issue and put your comment there. > > Marcus > > On 11 Jan 2016, at 09:56, Nicolai Hess <nicolaihess(a)gmail.com > <mailto:nicolaihess@gmail.com>> wrote: > > Can please someone translate / change the text in the > > Shortcut reminder Morph settings.( that got integrated in 50521) > > see my comment on > https://pharo.fogbugz.com/f/cases/17348/Enhance-shortcut-learnability#BugEv… > > and I asked for resubmitting the changes with proper author > initials > > instead of "tr" and if he signed the license agreement. > > Anyone knows more about "tr" ? > > And I am not sure if the right version is integrated. > > nicolai >

Jan. 13, 2016

Re: [Pharo-dev] How to get launcher launching Spur images?

by stepharo

So what is the conclusion? Can anybody get the launcher open both prespur and spur images? Stef Le 13/1/16 13:16, Blondeau Vincent a Ã©crit : > I confirm it works under W7 with Spur and not spur images. > Thanks ! > > I think https://github.com/pharo-project/pharo-launcher/issues/1 can be closed now? > > Vincent > >> -----Message d'origine----- >> De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de >> Stephan Eggermont >> EnvoyÃ© : mercredi 13 janvier 2016 12:35 >> Ã : pharo-dev(a)lists.pharo.org >> Objet : Re: [Pharo-dev] How to get launcher launching Spur images? >> >> On 13-01-16 12:25, Blondeau Vincent wrote: >>> Under Windows, this cmd is working: >>> OSProcess command: $" asString, vmCommand , '" "' , imagePath, '"'. >>> Does it work under Mac (with real double quotes and not 2 single quotes)? >>> If no, we should do something that is platform dependent.. >> Yes, it works. Please confirm if version 87 works for you >> >> Stephan >> >> > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Jan. 13, 2016

Re: [Pharo-dev] Problem with gitfiletree numeration

by Mariano Martinez Peck

On Wed, Jan 13, 2016 at 11:48 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > > > 2016-01-13 15:44 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> >> On Wed, Jan 13, 2016 at 11:33 AM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> >>> >>> 2016-01-13 14:32 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com> >>> : >>> >>>> >>>> On Wed, Jan 13, 2016 at 10:00 AM, Thierry Goubier < >>>> thierry.goubier(a)gmail.com> wrote: >>>> >>>>> >>>>> >>>>> 2016-01-13 13:56 GMT+01:00 Mariano Martinez Peck < >>>>> marianopeck(a)gmail.com>: >>>>> >>>>>> >>>>>> >>>>>> On Wed, Jan 13, 2016 at 9:27 AM, Thierry Goubier < >>>>>> thierry.goubier(a)gmail.com> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> 2016-01-13 13:12 GMT+01:00 Mariano Martinez Peck < >>>>>>> marianopeck(a)gmail.com>: >>>>>>> >>>>>>>> Hi guys, >>>>>>>> >>>>>>>> I wanted to know how you manage this situation. >>>>>>>> I had my already existing project in shub repo. Last version >>>>>>>> was OSSubprocess-MarianoMartinezPeck.43. I then created a github repo, >>>>>>>> cloned it, and then with gitfiletree I commit for the first time. >>>>>>>> >>>>>>>> The problem is that the commit I did with GitFileTree received this >>>>>>>> MC version: OSSubprocess-MarianoMartinezPeck.1. Normally I would not care. >>>>>>>> But in this case I do care because every in a while I would like to >>>>>>>> move/publish some versions from github to shub. And >>>>>>>> OSSubprocess-MarianoMartinezPeck.1 has 2 problems: >>>>>>>> >>>>>>>> 1) It has an older version number but newer contents >>>>>>>> >>>>>>> >>>>>>> >>>>>>>> 2) It's number is not unique. So if I copy versions created from >>>>>>>> github to shub, they would override those versiones created in shub (like >>>>>>>> the very old OSSubprocess-MarianoMartinezPeck.1 from shub) ?? >>>>>>>> >>>>>>> >>>>>>>> How do you normally solve this? >>>>>>>> >>>>>>> >>>>>>> The best is to move all the sthub versions on git, like that, >>>>>>> gitfiletree will number newer versions higher and this will work. >>>>>>> >>>>>>> >>>>>> OK, I got it. So you mean to use a Gofer pull/push operation to move >>>>>> all versions from shub to github, right? >>>>>> >>>>> >>>>> Yes! >>>>> \ >>>>> >>>> >>>> OK, I did that. Problem is I had screwed up the first version. Because >>>> now in gitfiletree repo, the OSSubprocess-MarianoMartinezPeck.1 is the >>>> "new one" and not the old from shub. I suspect this could bring problems >>>> for history changes, etc... >>>> >>> >>> >>>> Is there a way I can revert and copy the original >>>> OSSubprocess-MarianoMartinezPeck.1 from shub and override the >>>> OSSubprocess-MarianoMartinezPeck.1 from gitfiletree? >>>> >>> >>> Yes. You can reset in git to a previous commit, I think it is with git >>> --reset . >>> >>> But this is problematic if it was pushed on github. >>> >>> >>>> >>>> Or...at least a way to remove everything and start fresh with the >>>> fecth/push??? >>>> >>> >>> Yes, but, again, problematic if it was pushed to github. >>> >>> Thierry >>> >> >> It was pushed to github :( >> >> > :( But deleting on github, resetting on your own repo, recreating on > github and pushing shouldn't take you very long. > > Thanks! That was easy indeed :) > >> Let me ask... do you think my assumption is correct that it could bother >> me when watching the history via MC browser, or a merge or .. any kind of >> MC operation that would be screw up because of this? >> If this is not the case, then...ok, I can live with that mistake. >> > > No, it shouldn't bother you neither make any operation problematic. > > Thierry > > >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- Mariano http://marianopeck.wordpress.com

Jan. 13, 2016

Re: [Pharo-dev] Problem with gitfiletree numeration

by Thierry Goubier

2016-01-13 15:46 GMT+01:00 David Allouche <david(a)allouche.net>: > > On 13 Jan 2016, at 15:33, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > 2016-01-13 14:32 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> On Wed, Jan 13, 2016 at 10:00 AM, Thierry Goubier < >> thierry.goubier(a)gmail.com> wrote: >> >>> >>> >>> 2016-01-13 13:56 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com> >>> : >>> >>>> >>>> >>>> On Wed, Jan 13, 2016 at 9:27 AM, Thierry Goubier < >>>> thierry.goubier(a)gmail.com> wrote: >>>> >>>>> >>>>> >>>>> 2016-01-13 13:12 GMT+01:00 Mariano Martinez Peck < >>>>> marianopeck(a)gmail.com>: >>>>> >>>>>> Hi guys, >>>>>> >>>>>> I wanted to know how you manage this situation. >>>>>> I had my already existing project in shub repo. Last version >>>>>> was OSSubprocess-MarianoMartinezPeck.43. I then created a github repo, >>>>>> cloned it, and then with gitfiletree I commit for the first time. >>>>>> >>>>>> The problem is that the commit I did with GitFileTree received this >>>>>> MC version: OSSubprocess-MarianoMartinezPeck.1. Normally I would not care. >>>>>> But in this case I do care because every in a while I would like to >>>>>> move/publish some versions from github to shub. And >>>>>> OSSubprocess-MarianoMartinezPeck.1 has 2 problems: >>>>>> >>>>>> 1) It has an older version number but newer contents >>>>>> >>>>> >>>>> >>>>>> 2) It's number is not unique. So if I copy versions created from >>>>>> github to shub, they would override those versiones created in shub (like >>>>>> the very old OSSubprocess-MarianoMartinezPeck.1 from shub) ?? >>>>>> >>>>> >>>>>> How do you normally solve this? >>>>>> >>>>> >>>>> The best is to move all the sthub versions on git, like that, >>>>> gitfiletree will number newer versions higher and this will work. >>>>> >>>>> >>>> OK, I got it. So you mean to use a Gofer pull/push operation to move >>>> all versions from shub to github, right? >>>> >>> >>> Yes! >>> \ >>> >> >> OK, I did that. Problem is I had screwed up the first version. Because >> now in gitfiletree repo, the OSSubprocess-MarianoMartinezPeck.1 is the >> "new one" and not the old from shub. I suspect this could bring problems >> for history changes, etc... >> > > >> Is there a way I can revert and copy the original >> OSSubprocess-MarianoMartinezPeck.1 from shub and override the >> OSSubprocess-MarianoMartinezPeck.1 from gitfiletree? >> > > Yes. You can reset in git to a previous commit, I think it is with git > --reset . > > But this is problematic if it was pushed on github. > > >> >> Or...at least a way to remove everything and start fresh with the >> fecth/push??? >> > > Yes, but, again, problematic if it was pushed to github. > > Thierry > > > > Removing commits from a git branch is only really problematic if there are > outstanding, unmerged branches out there, since it tends to cause false > merge conflicts. > > Locals clones of the public repository WILL complain about a divergence, > but they can be fixed by "git pull --force". That is probably acceptable in > your context, since you appear to be in a "botched history" situation. > > Taking a step back, any distributed version control that uses explicit > revision numbers for ordering is broken by design. Yes, Monticello, I am > looking at you. > > That was one of the design mistakes of GNU Arch, and the reason why all > the DVCS that followed it (bzr, hg, git) identify revisions by UUIDs and > define ordering exclusively by the ancestry graph. Experience has also > shown that using content-based UUIDs like hg and git is preferable, for > performance and integrity, to using arbitrary UUIDs like bzr did. > Good to know. I note the ordering by ancestry graph point; I think this could be significant. > > Disclaimer: I am (not yet) familiar with the Monticello model, so I might > be all wrong. But I am quite knowledgeable about DVCS design in general. > Monticello uses explicit revision numbers for ordering and version identification, has access to the full ancestry (in theory; in practice not[*]), and, rarely, uses arbitrary UUIDs to identify versions. Thierry [*] For the Pharo3 release, the ancestry of all core packages was erased from those packages because it was too large.

Jan. 13, 2016

Re: [Pharo-dev] Problem with gitfiletree numeration

by Thierry Goubier

2016-01-13 15:44 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Wed, Jan 13, 2016 at 11:33 AM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> >> >> 2016-01-13 14:32 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> >>> On Wed, Jan 13, 2016 at 10:00 AM, Thierry Goubier < >>> thierry.goubier(a)gmail.com> wrote: >>> >>>> >>>> >>>> 2016-01-13 13:56 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com >>>> >: >>>> >>>>> >>>>> >>>>> On Wed, Jan 13, 2016 at 9:27 AM, Thierry Goubier < >>>>> thierry.goubier(a)gmail.com> wrote: >>>>> >>>>>> >>>>>> >>>>>> 2016-01-13 13:12 GMT+01:00 Mariano Martinez Peck < >>>>>> marianopeck(a)gmail.com>: >>>>>> >>>>>>> Hi guys, >>>>>>> >>>>>>> I wanted to know how you manage this situation. >>>>>>> I had my already existing project in shub repo. Last version >>>>>>> was OSSubprocess-MarianoMartinezPeck.43. I then created a github repo, >>>>>>> cloned it, and then with gitfiletree I commit for the first time. >>>>>>> >>>>>>> The problem is that the commit I did with GitFileTree received this >>>>>>> MC version: OSSubprocess-MarianoMartinezPeck.1. Normally I would not care. >>>>>>> But in this case I do care because every in a while I would like to >>>>>>> move/publish some versions from github to shub. And >>>>>>> OSSubprocess-MarianoMartinezPeck.1 has 2 problems: >>>>>>> >>>>>>> 1) It has an older version number but newer contents >>>>>>> >>>>>> >>>>>> >>>>>>> 2) It's number is not unique. So if I copy versions created from >>>>>>> github to shub, they would override those versiones created in shub (like >>>>>>> the very old OSSubprocess-MarianoMartinezPeck.1 from shub) ?? >>>>>>> >>>>>> >>>>>>> How do you normally solve this? >>>>>>> >>>>>> >>>>>> The best is to move all the sthub versions on git, like that, >>>>>> gitfiletree will number newer versions higher and this will work. >>>>>> >>>>>> >>>>> OK, I got it. So you mean to use a Gofer pull/push operation to move >>>>> all versions from shub to github, right? >>>>> >>>> >>>> Yes! >>>> \ >>>> >>> >>> OK, I did that. Problem is I had screwed up the first version. Because >>> now in gitfiletree repo, the OSSubprocess-MarianoMartinezPeck.1 is the >>> "new one" and not the old from shub. I suspect this could bring problems >>> for history changes, etc... >>> >> >> >>> Is there a way I can revert and copy the original >>> OSSubprocess-MarianoMartinezPeck.1 from shub and override the >>> OSSubprocess-MarianoMartinezPeck.1 from gitfiletree? >>> >> >> Yes. You can reset in git to a previous commit, I think it is with git >> --reset . >> >> But this is problematic if it was pushed on github. >> >> >>> >>> Or...at least a way to remove everything and start fresh with the >>> fecth/push??? >>> >> >> Yes, but, again, problematic if it was pushed to github. >> >> Thierry >> > > It was pushed to github :( > > :( But deleting on github, resetting on your own repo, recreating on github and pushing shouldn't take you very long. > > Let me ask... do you think my assumption is correct that it could bother > me when watching the history via MC browser, or a merge or .. any kind of > MC operation that would be screw up because of this? > If this is not the case, then...ok, I can live with that mistake. > No, it shouldn't bother you neither make any operation problematic. Thierry > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Jan. 13, 2016