Am 17.09.2014 um 20:59 schrieb Jussi Lahtinen:
>> No, that ist for detection of file corruption on disk. Or even file
>> corruption in general.
>>
> Hmmm... I wonder what is the difference exactly. How svn can detect
> conflict, if it cannot detect corruption?
Hmmm... :-), too complicated for me
> No, that ist for detection of file corruption on disk. Or even file
> corruption in general.
>
Hmmm... I wonder what is the difference exactly. How svn can detect
conflict, if it cannot detect corruption?
> Now start coding and committing by and by.
>
What I didn't like is the way you need
Am 17.09.2014 um 17:15 schrieb Jussi Lahtinen:
>> http://git-scm.com/docs/git-checkout
>>
>> git co changes the working tree.
>
> Seems it doesn't just switch.
> "Updates files in the working tree to match the version in the index or the
> specified tree."
Yes shure, all different files in the th
One more thing is disk space. With SVN there are two entire copies of
the repo. On Git there is one and all the rest are diffs.
On the corruption front it works by sha hashing so you are
mathematically guaranteed that the code is sound!
On 17/09/14 17:22, Christof Thalhofer wrote:
> Am 17.09.201
Am 17.09.2014 um 16:39 schrieb Jussi Lahtinen:
>> 1) SVN will not detect a corruption - with Git the sha1 hash will
>> confirm that your source is unadulterated no matter who you pull it from.
>
> Applies to situation where there is more than one repo where to pull. AFAIK
> there isn't for Gambas.
Just watch the Linus 2007 video and make your own mind up.
On 17/09/14 15:39, Jussi Lahtinen wrote:
>> 1) SVN will not detect a corruption - with Git the sha1 hash will
>> confirm that your source is unadulterated no matter who you pull it from.
>>
>
> Applies to situation where there is more tha
> http://git-scm.com/docs/git-checkout
>
> git co changes the working tree.
>
Seems it doesn't just switch.
"Updates files in the working tree to match the version in the index or the
specified tree."
Jussi
--
Want excit
Am 17.09.2014 um 16:27 schrieb Jussi Lahtinen:
>>> git checkout pristine-tar
>>> git checkout upstream
>>> git checkout master
>>
>> Thats silly. git checkout just changes branches. In this example you
>> switch between three branches and do nothing.
>
> Well this is what the admin of the git repo
> 1) SVN will not detect a corruption - with Git the sha1 hash will
> confirm that your source is unadulterated no matter who you pull it from.
>
Applies to situation where there is more than one repo where to pull. AFAIK
there isn't for Gambas.
> 2) With SVN, all your eggs are in one basket -
> > git checkout pristine-tar
> > git checkout upstream
> > git checkout master
>
> Thats silly. git checkout just changes branches. In this example you
> switch between three branches and do nothing.
>
Well this is what the admin of the git repository told me to do. I tried
several times, and thi
Am 17.09.2014 um 03:19 schrieb Jussi Lahtinen:
> git checkout pristine-tar
> git checkout upstream
> git checkout master
Thats silly. git checkout just changes branches. In this example you
switch between three branches and do nothing.
BTW. Git is phantastic. I was coming from CVS to SVN and hal
Hi Jussi,
I hope I have clicked the right reply button.
I do not recognise the work flow you have annotated. I think there are
many approaches that fit particular needs. Staging/non staging etc.
The most significant features are:-
1) SVN will not detect a corruption - with Git the sha1 hash will
With svn you just checkout, edit the source if you want, and then compile.
But with git, it requires something very different...
git clone
git checkout pristine-tar
git checkout upstream
git checkout master
git-buildpackage -us -uc
I don't know what those commands do, but they were advised and ob
> Do I have to question my understanding of criticism? I really think this
> is criticism and where I come from this is nothing bad. Especially if the
> criticising person does it the conciliatory way :-)
Thank you. Here, many will take their bat home if an outsider expresses
an alternative view t
Le 16/09/2014 23:04, John Leake a écrit :
> Back on topic re Subject. If in the IDE you select a ToggleButton and
> set its Foreground or Background colour and then later wish put either
> back to its default (by selecting the control, then highlighting the
> property and pressing delete) the cont
On Tue, 16 Sep 2014, John Leake wrote:
> > The "delete" key is the shortcut for deleting the control. Use the
> > "backspace" key for voiding the property.
> Sorry guys this is inconsistent and unintuitive and will drive newbies
> away for sure.
>
> Where does it tell the user that this is so. If
Hi guys,
ToolTip has the behaviour as Text property.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.
> The "delete" key is the shortcut for deleting the control. Use the
> "backspace" key for voiding the property.
Sorry guys this is inconsistent and unintuitive and will drive newbies
away for sure.
Where does it tell the user that this is so. If you double click the
text property it is highlight
On Tue, 16 Sep 2014, John Leake wrote:
> On 16/09/14 22:04, John Leake wrote:
> > Back on topic re Subject. If in the IDE you select a ToggleButton and
> > set its Foreground or Background colour and then later wish put either
> > back to its default (by selecting the control, then highlighting th
Le 16/09/2014 23:09, John Leake a écrit :
> On 16/09/14 22:04, John Leake wrote:
>> Back on topic re Subject. If in the IDE you select a ToggleButton and
>> set its Foreground or Background colour and then later wish put either
>> back to its default (by selecting the control, then highlighting th
On 16/09/14 22:04, John Leake wrote:
> Back on topic re Subject. If in the IDE you select a ToggleButton and
> set its Foreground or Background colour and then later wish put either
> back to its default (by selecting the control, then highlighting the
> property and pressing delete) the control i
Back on topic re Subject. If in the IDE you select a ToggleButton and
set its Foreground or Background colour and then later wish put either
back to its default (by selecting the control, then highlighting the
property and pressing delete) the control is deleted instead of the
property.
-
>> P.S. I don't know why I keep going to the wrong place in the help. Also
I usually use a web search engine with my problem which invariably
directs me to:
http://gambasdoc.org/help/doc/whatever
which so far has fallen short of giving me enough info to sort thing out
without pestering the mailing
On Tue, 16 Sep 2014, John Leake wrote:
> Hi Tobi,
>
> Thanks. A link to [0] in 'Compiling the Subversion repository' would
> save you a bit of email noise.
>
Sort of done.
> [System]
> Gambas=3.5.4
> OperatingSystem=Linux
> Kernel=3.11.0-26-generic
> Architecture=x86_64
> Distribution=Ubuntu 12
Hi Tobi,
Thanks. A link to [0] in 'Compiling the Subversion repository' would
save you a bit of email noise.
[System]
Gambas=3.5.4
OperatingSystem=Linux
Kernel=3.11.0-26-generic
Architecture=x86_64
Distribution=Ubuntu 12.04.5 LTS
Desktop=XFCE
Theme=QGtk
Language=en_GB.UTF-8
Memory=7863M
[Librarie
On Tue, 16 Sep 2014, John Leake wrote:
> I followed the docs for v3
> Compiling the Subversion repository.
>
> I checked out trunk and did
>
> $ ./reconf-all
> ...
> $ ./configure -C
>
> But there are lots of inaccessible header files.
>
> Attached the config.log
Did you see [0]? Your attachme
I followed the docs for v3
Compiling the Subversion repository.
I checked out trunk and did
$ ./reconf-all
...
$ ./configure -C
But there are lots of inaccessible header files.
Attached the config.log
config.log.tar.gz
Description: GNU Zip compressed data
-
>
> I'm talking about the development version.
>
Sorry, no wonder you want to get it out quickly.
Will down load, build and report back.
--
Want excitement?
Manually upgrade your production database.
When you want reliab
Le 16/09/2014 17:16, John Leake a écrit :
> Hi All,
> I cannot see any change in back/fore colour change on any control.
> Should this work OK ?
>
> [System]
> Gambas=3.5.4
> OperatingSystem=Linux
> Kernel=3.11.0-26-generic
> Architecture=x86_64
> Distribution=Ubuntu 12.04.5 LTS
> Desktop=XFCE
> Th
Hi All,
I cannot see any change in back/fore colour change on any control.
Should this work OK ?
[System]
Gambas=3.5.4
OperatingSystem=Linux
Kernel=3.11.0-26-generic
Architecture=x86_64
Distribution=Ubuntu 12.04.5 LTS
Desktop=XFCE
Theme=QGtk
Language=en_GB.UTF-8
Memory=7863M
[Libraries]
Cairo=libc
30 matches
Mail list logo
