On Sun, 15 Jan 2017 14:53:31 +0100, Peter Uhnak wrote:
I find these endless git vs monticello discussions confusing and
pointless.
+ 1
:)
Maybe we can hang Q&A list somewhere on pharo website to point to?
Because git is getting increased traction in Pharo, so the same
questions an
On 16/01/17 07:34, Pierce Ng wrote:
On Sun, Jan 15, 2017 at 08:09:28AM -0500, Offray Vladimir Luna Cárdenas wrote:
That's the core idea of fossil. "GitHub alike in a box" DVCS with
tickets, wiki, web server/GUI in 2 MB.
Hi Offray,
Do you use Fossil with Pharo source code? Just store mcz file
Several things I disagree with [1]
1) "Living in the image" , I think this is a usual smalltalker
misconception in that just because you do not see something it means it
does not exist.
Obviously thats not the case with the Pharo image. The Pharo image is
indeed a binary file and self contained e
On 01/16/2017 12:20 PM, Peter Uhnak wrote:
Usually it's better to keep the discussion contained on the mailing list, and
not extend it to private conversations.
Hi Peter,
after your message i considered the the thread to be essentially closed.
My point was that not only you don't understand gi
On Sun, Jan 15, 2017 at 08:09:28AM -0500, Offray Vladimir Luna Cárdenas wrote:
> That's the core idea of fossil. "GitHub alike in a box" DVCS with
> tickets, wiki, web server/GUI in 2 MB.
Hi Offray,
Do you use Fossil with Pharo source code? Just store mcz files as blobs?
Pierce
I gave a talk at Smalltalks 2016 entitled: "Dangerous Liaisons:
Smalltalk, files, and git"[1] and this thread is a perfect example the
dangers I was thinking about:).
For "history buffs", here's a link for my talk at STIC 2012 entitled
"Practical Git for Smalltalk"[2].
Dale
[1] http://fast.
For those that lost track of the purpose of this thread let me provide a
summary
The discussion started from the Google Visibility where Sven asked me why I
find the Pharo VCS and Monticello a very problematic implementation
I decided to reply creating a separate thread in order to not hijack the
I find these endless git vs monticello discussions confusing and pointless.
Maybe we can hang Q&A list somewhere on pharo website to point to? Because git
is getting increased traction in Pharo, so the same questions and endless
discussions will popup over and over again.
1. Some people here ar
On 15/01/17 04:29, itli...@schrievkrom.de wrote:
I also have thought several times that it would be nice to have a SQLite
database holding all sources/packages. How much easier life would be
with that.
That's the core idea of fossil. "GitHub alike in a box" DVCS with
tickets, wiki, web ser
I am also amazed at the number of people not using basic git UI tools, like
"git gui" and "gitk" + mergetool/difftool settings in the git config
(kdiff3, meld, WinMerge, difuse) which make the work of merging so much
easier (e.g. "git difftool" or "git mergetool" on the CLI when one
encounters issu
My reasons to like the legacy/mcz style [D]VCS in Pharo:
1) No fuss in saving things when I am starting something
2) Easy to explain to someone new to Pharo
3) Can use any FTP server as a repo (Useful when in a walled garden)
4) Compatible with the package cache, so I can collect mcz's from variou
> Am 15.01.2017 um 10:29 schrieb "itli...@schrievkrom.de"
> :
>
> I would give you many more "+" - if you wish - for your opinion:
>
>
>
>
> Another point I would like to mention: keep the source code locally or
> at least have an easy
I would give you many more "+" - if you wish - for your opinion:
Another point I would like to mention: keep the source code locally or
at least have an easy option to hold all source code locally.
I've seen so many times, that git or one
Hi Dimitris,
i as a simple user tend to think about these things in simple terms: i
download a program, add something, upload my addition. lets take an
upload step, _one_ simple step with monticello: i upload something once
(git add), i upload it a second time (git commit), i upload it a third
On 14/01/17 09:14, Dimitris Chloupis wrote:
[...]
Remember we have to compete with languages like Ruby and Python .
[...]
And in the live coding and moldability camp the competition goes pretty
well (Ruby has Sonic Pi, Python has Jupyter, for other audience, but
none of those are as mold
We agree that we disagree, that's ok , we all have our own ways we like to
work.
On Sat, 14 Jan 2017 at 17:08, Sven Van Caekenberghe wrote:
> We disagree, I should not have responded.
>
>
>
> Eclipse, IntelliJ, Emacs and so many other IDEs with massive user bases
> all try to make things nice an
We disagree, I should not have responded.
Eclipse, IntelliJ, Emacs and so many other IDEs with massive user bases all try
to make things nice and easy to use inside their own IDE, to give developers a
cool, intelligent, language aware workflow. Of course Pharo wants to do the
same without being
On Sat, Jan 14, 2017 at 3:21 PM Sven Van Caekenberghe wrote:
>
> > On 14 Jan 2017, at 12:58, Dimitris Chloupis
> wrote:
> >
> > I fail to see what is user friendly about Monticello , I find its GUI
> and the total workflow really bad, certainly the worst VCS GUI I have ever
> used. But I will ad
18 matches
Mail list logo
