On 06/07/2017 04:49 AM, Graeme Geldenhuys wrote:
On 2017-06-07 08:24, Giuliano Colla wrote:
One of the important things of programming, both for economical reasons
and for better quality, is to be able to reuse code modules.
Strange that in my 25+ years of programming I have never needed that.
Il 07/06/2017 10:49, Graeme Geldenhuys ha scritto:
Strange that in my 25+ years of programming I have never needed that.
Somehow I always managed just fine, and relied or more reliable
sources of information for version control and reusable code modules.
Well each one selects its way of workin
On 2017-06-07 07:02, Bo Berglund wrote:
So time stamp handling is not that important really it's just that I
observed the difference when comparing the GIT version of a project
Fair enough and a good observation.
Git stores such "metadata" like author name + email, authored timestamp,
committ
On 2017-06-07 08:24, Giuliano Colla wrote:
One of the important things of programming, both for economical reasons
and for better quality, is to be able to reuse code modules.
Strange that in my 25+ years of programming I have never needed that.
Somehow I always managed just fine, and relied o
Il 07/06/2017 00:38, Graeme Geldenhuys ha scritto:
You are the second person I hear say that. Why is preserving
timestamps important? What use is there for it?
One of the important things of programming, both for economical reasons
and for better quality, is to be able to reuse code modules.
On Tue, 6 Jun 2017 12:30:58 +0200, Giuliano Colla
wrote:
>Il 06/06/2017 10:40, Bo Berglund ha scritto:
>> Relevant files compare fine
>> except they are not the correct timestamp.
>
>This is one of the down sides of GIT: it doesn't preserve timestamps.
>
>As a workaround you may write a small scr
On Tue, 6 Jun 2017 23:25:03 +0100, Graeme Geldenhuys
wrote:
>> So it tries to "fix" this by making fake commits or something similar.
>
>I guess its trying to fix a hack with a hack. ;-)
>
I will have to get into understanding GIT operations more so I can see
the existing tags, right now I am
On 2017-06-06 11:30, Giuliano Colla wrote:
This is one of the down sides of GIT: it doesn't preserve timestamps.
You are the second person I hear say that. Why is preserving timestamps
important? What use is there for it?
Git already tracks the commit date/time, authored date/time and other
On 2017-06-06 09:40, Bo Berglund wrote:
It seems like GIT does not like the fact that in CVS only changed
files can be committed thus revisions of files evolve on a file by
file basis. So when a CVS tag operation is performed the tag is
applied on all of the files in the current state. This means
Il 06/06/2017 10:40, Bo Berglund ha scritto:
Relevant files compare fine
except they are not the correct timestamp.
This is one of the down sides of GIT: it doesn't preserve timestamps.
As a workaround you may write a small script which will touch each file
of the newly created repository wit
On Mon, 5 Jun 2017 15:46:43 +0100, Graeme Geldenhuys
wrote:
>1) I suggest you start with a 'gitk --all' and see how the history
>of your repository looks like, and if there is any history at all.
The history is there all right, but I think that the tags are a bit
different...
It seems like G
On 04/06/17 23:12, Bo Berglund wrote:
> Report on progress:
> I have found a way to convert CVS to GIT using the cvs2svn module,
> which contains a cvs2git file. It was described in this article:
> https://devsector.wordpress.com/2014/05/17/migrate-cvs-to-git-with-cvs2svn/
>
[...]
>
> I am worryi
On 2017-06-04 23:12, Bo Berglund wrote:
Why is the repo in this condition?
And what to do about it? Obviously going over it with
git reset HEAD ...
isn't really practical since this example project (an Android App)
contains deeply nested folder trees with hundreds of files.
Like I said, I have
On 30/05/17 14:30, Graeme Geldenhuys wrote:
On 2017-05-29 13:01, Mark Morgan Lloyd wrote:> I'd use something like an
HP> Microserver with at least mirrored discs,
Yes the HP Microservers are excellent! I highly recommend them, and they
are cheap as chips - so a real bargain. I would load it with
Report on progress:
I have found a way to convert CVS to GIT using the cvs2svn module,
which contains a cvs2git file. It was described in this article:
https://devsector.wordpress.com/2014/05/17/migrate-cvs-to-git-with-cvs2svn/
Since our CVS server resides on Windows and is driven by CVSNT and the
On Fri, 2 Jun 2017 10:19:49 +0100, Graeme Geldenhuys
wrote:
>On 2017-06-02 00:00, Bo Berglund wrote:
>> The beauty of this is that we do not need to duplicate common
>> functionality between projects as would be the case if we *copied* the
>> common files into the source folder. These files are u
On 2017-06-02 00:00, Bo Berglund wrote:
The beauty of this is that we do not need to duplicate common
functionality between projects as would be the case if we *copied* the
common files into the source folder. These files are used in many
places but versioned in a single place on the server.
Ye
On 01/06/17 09:12, Graeme Geldenhuys wrote:
> On 2017-05-31 08:33, Lukasz Sokol wrote:
>> TortoiseGIT also lets you create a 'bare' repo.
>
> I don't disputed that, and I don't mind others using gui front-ends
> to git - as long as they know they are seriously limiting their
> abilities and functi
Continuing with GIT...
I am now studying a few on-line documents outlining the conversion of
a CVS repository to GIT. There is a script suite named cvs2svn with a
number of specific scripts for various targets like cvs2git, so I
think I can use this. But I think I have found a problem, which may o
On 2017-06-01 08:54, Bo Berglund wrote:
Even though it now works it would be intersting to know *why* I had to
log off and back on for it to use the path ...
It seems quite clearly that the PATH doesn't fully take affect (in all
sessions - it definitely doesn't in existing open sessions) until
On 2017-05-31 08:33, Lukasz Sokol wrote:
TortoiseGIT also lets you create a 'bare' repo.
I don't disputed that, and I don't mind others using gui front-ends to
git - as long as they know they are seriously limiting their abilities
and functionality of Git.
I have reviewed a lot of Git GUI f
On Wed, 31 May 2017 23:04:02 +0200, Bo Berglund
wrote:
>Now remains to find out how to disable the old version shipped with
>Raspbian and use the self-compiled newer version.
>The $PATH location seems not to help.
>
Problem solved but not understanding why...
I logged off the PuTTY session and t
On 31/05/17 01:03, Graeme Geldenhuys wrote:
> On 2017-05-30 22:19, Bo Berglund wrote:
>> Since my local system is a Windows 7 laptop I have to resort to an RPi
>> to get the Linux system for which the commands are native...
>
> Git is native on all supported platforms now.
>
>>
>>> mkdir /data/
On Wed, 31 May 2017 22:23:30 +0200, Bo Berglund
wrote:
>On Wed, 31 May 2017 15:42:48 -0400, wkitt...@windstream.net wrote:
>
>>at the command line, type in "which git" without the double quotes...
>
Now I made a test by looking at another RPi3 with Raspbian Jessie
where I have definitely NOT been
On Wed, 31 May 2017 15:42:48 -0400, wkitt...@windstream.net wrote:
>On 05/31/2017 02:13 PM, Bo Berglund wrote:
>> the response to git --version is still
>> 2.1.4
>>
>> From where does this come???
>
>
>at the command line, type in "which git" without the double quotes...
$ which git
/home/pi/bi
On 05/31/2017 02:13 PM, Bo Berglund wrote:
the response to git --version is still
2.1.4
From where does this come???
at the command line, type in "which git" without the double quotes...
--
NOTE: No off-list assistance is given without prior approval.
*Please keep mailing list traf
On Wed, 31 May 2017 18:04:28 +0100, Graeme Geldenhuys
wrote:
>On 2017-05-31 16:10, Bo Berglund wrote:
>
>> Is it not possible to put docs and info below the ~/ dir?
>> According to the INSTALL file on the subject of Git install it says:
>
>Yes, it works like most Makefile based environments - and
On 2017-05-31 16:10, Bo Berglund wrote:
The apt-get version of the git I use now is:
~/ $git --version
git version 2.1.4
Yeah, that is a rather old version. The latest is v2.13.
$ git tag
will show all tagged releases. Just look for the latest one. You can
also use 'gitk --all' and see wha
On Wed, 31 May 2017 10:58:29 +0200, Bo Berglund
wrote:
>>I always install git
>>from source code and compile it myself (like I do with FPC and Lazarus
>>too). Everything is then included - as it should be. Linux distros f*ck
>>everything up and split it into multiple packages. eg: git-core,
>
On 2017-05-31 09:58, Bo Berglund wrote:
Aplogies if my postings are a bit longish,
You are like me then. :) I try to write shorter messages, but often fail.
Access via http would probably be the simplest way to manage I
believe.
I actually found Gitolite the simplest (which uses SSH and m
On Wed, 31 May 2017 01:03:54 +0100, Graeme Geldenhuys
wrote:
Graeme, I am very grateful for your contribution to this discussion!
Aplogies if my postings are a bit longish, but I try to convey my
concerns and ignorance...
>> So this should not be created inside some user home then?
>
>You can cr
On 2017-05-30 22:19, Bo Berglund wrote:
Since my local system is a Windows 7 laptop I have to resort to an RPi
to get the Linux system for which the commands are native...
Git is native on all supported platforms now.
mkdir /data/myremote.git
cd /data/myremote.git
git init --share --b
On Tue, 30 May 2017 15:37:30 +0100, Graeme Geldenhuys
wrote:
>On 2017-05-30 06:53, Bo Berglund wrote:
>> OK, I did not have in mind to use an RPi3 as the final system. I just
>> wanted to acquaint myself with GIT using a small portable unit over
>> the summer.
>
>In that case, you don't even need
Hi,
On 30/5/2017 5:19 μμ, Graeme Geldenhuys wrote:
Run FreeBSD or Linux with ZFS in RAID-z1 or RAID-z2.
What a coincidence, we scheduled to test OmniOS with napp-it in a HP
MicroServer . ;)
https://www.napp-it.org/downloads/omnios_en.html .
regards,
--
Dimitrios Chr. Ioannidis
On 30/05/17 14:30, Graeme Geldenhuys wrote:
Run FreeBSD or Linux with ZFS in
RAID-z1 or RAID-z2. Like I said is some other thread, I wouldn't trust
my data on any other file system again - only ZFS for me! A all-in-one
easy to set up system is FreeNAS (which comes standard with ZFS) and
includes
Il 29/05/2017 13:00, Bo Berglund ha scritto:
Any suggestions on where to start?
My suggestion would be to use http://rogerdudler.github.io/git-guide/ as
a quick reference just to have at hand the syntax of the most used
commands, together with the links to the full documentation.
IMO a new
On 2017-05-30 06:53, Bo Berglund wrote:
OK, I did not have in mind to use an RPi3 as the final system. I just
wanted to acquaint myself with GIT using a small portable unit over
the summer.
In that case, you don't even need a RPi... Simply practice by doing the
following on your local system:
On 2017-05-29 12:00, Bo Berglund wrote:
Is there a good way to set up an RPi3 box as a GIT server and get
going with that?
Can GIT work in a way that would be comparable to CVS regarding
concurrent development etc?
Any suggestions on where to start?
Git doesn't require a "server" - there is n
On 2017-05-29 13:01, Mark Morgan Lloyd wrote:
I'd use something like an HP
Microserver with at least mirrored discs,
Yes the HP Microservers are excellent! I highly recommend them, and they
are cheap as chips - so a real bargain. I would load it with good
NAT/Server style disks (eg: Western D
On Mon, 29 May 2017 12:01:32 +, Mark Morgan Lloyd
wrote:
>On 29/05/17 11:12, Bo Berglund wrote:
>
>> TestingSo I thought that one way to go forward was for me to use an
>> RPi3 boxas a repository server with GIT or whatever (seems like the
>> CVSsuccessor SVN is now also on the decl
On 29/05/17 11:12, Bo Berglund wrote:
TestingSo I thought that one way to go forward was for me to use an
RPi3 boxas a repository server with GIT or whatever (seems like the
CVSsuccessor SVN is now also on the decline...).Is there a good way to set up
an RPi3 box as a GIT server and g
I have followed parts of the very long thread "GIT & SVN" and found it
informative and partly amusing too...
Since I am still on CVS it really was getting me to think about new
version control systems and especially GIT since Graeme is pushing so
hard for it.
Background:
---
I have a small
42 matches
Mail list logo
