Graeme Geldenhuys schrieb:
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
Git for our company repositories. In SubVersion, branching is like an
afterthought. Manually having to track merges to a branch (though
apparently there was been some work towards this), etc...
This is
Graeme Geldenhuys escribió:
Hi,
Seeing that Lazarus and FPC are reasonable sized projects and have
been using SubVersion for some time, there should be a few SubVersion
experts around.
Have any of you weighed up the pros and cons between SubVersion and
Git? Has FPC or Lazarus team ever
On 11/5/08, Graeme Geldenhuys [EMAIL PROTECTED] wrote:
* Git repositories are MUCH smaller. SubVersion has duplicates of each
file which actually more than doubles the size of a repository.
This is impressive. Mozilla has 10 years of history in their
SubVersion repository totalling 12Gig of
Graeme Geldenhuys schrieb:
Hi,
Seeing that Lazarus and FPC are reasonable sized projects and have
been using SubVersion for some time, there should be a few SubVersion
experts around.
Have any of you weighed up the pros and cons between SubVersion and
Git? Has FPC or Lazarus team ever
Graeme Geldenhuys schrieb:
On 11/5/08, Graeme Geldenhuys [EMAIL PROTECTED] wrote:
* Git repositories are MUCH smaller. SubVersion has duplicates of each
file which actually more than doubles the size of a repository.
This is impressive. Mozilla has 10 years of history in their
SubVersion
On Wed, Nov 5, 2008 at 18:02, Florian Klaempfl [EMAIL PROTECTED] wrote:
Git is a hype. Git might be nice for projects with 100 developers and
which has (like linux) dedicated branch maintainers. Git allows to
support complicated project structures with several layers of
maintainers and project
Alexander Klenin schrieb:
On Wed, Nov 5, 2008 at 18:02, Florian Klaempfl [EMAIL PROTECTED] wrote:
Git is a hype. Git might be nice for projects with 100 developers and
which has (like linux) dedicated branch maintainers. Git allows to
support complicated project structures with several layers
Florian Klaempfl schrieb:
But at least speaking for FPC: anybody interested in FPC development can
get write access to own svn branchs where he can do his development on
FPC. Using svnmerge, merging of such branches is very easy. This has
also the advantage that changes don't get lost in
On 11/5/08, Reenen Laurie [EMAIL PROTECTED] wrote:
Git has - like several other linux applications - a crappy name. I dunno if
it is a dirty word, but it sounds like one.
:-)
I do not want a whole history of edits if I only want to check-out (svn
terminology) the latest version.
Git does
2008/11/5 Reenen Laurie [EMAIL PROTECTED]:
Git has - like several other linux applications - a crappy name. I dunno if
it is a dirty word, but it sounds like one.
in the u.k. we use it like bastard, e.g. linus is an old git.
henry
___
Lazarus
On 11/5/08, Alexander Klenin [EMAIL PROTECTED] wrote:
They are usually of about equal size, for example, svn checkout of
Pidgin (IM tool) is 122 MB while complete history in Git repository is 148
MB.
I don't think that is incorrect. The svn checkout will only contain
the last revision (no
Graeme Geldenhuys schrieb:
On 11/5/08, Alexander Klenin [EMAIL PROTECTED] wrote:
They are usually of about equal size, for example, svn checkout of
Pidgin (IM tool) is 122 MB while complete history in Git repository is 148
MB.
I don't think that is incorrect. The svn checkout will only
On 11/5/08, Reenen Laurie [EMAIL PROTECTED] wrote:
Git has - like several other linux applications - a crappy name. I dunno if
it is a dirty word, but it sounds like one.
The text below is quoted from: http://git.or.cz/gitwiki/GitFaq
-
Why the 'git' name?
Quoting
Graeme Geldenhuys schrieb:
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
This is impressive. Mozilla has 10 years of history in their
SubVersion repository totalling 12Gig of information. SubVersion also
requires over 240,000 files in a single directory to handle the
+240,000
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
This is impressive. Mozilla has 10 years of history in their
SubVersion repository totalling 12Gig of information. SubVersion also
requires over 240,000 files in a single directory to handle the
+240,000 commits.
And who cares?
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
Git is a hype. Git might be nice for projects with 100 developers and
which has (like linux) dedicated branch maintainers. Git allows to
support complicated project structures with several layers of
maintainers and project managers. But
On 11/5/08, Vincent Snijders [EMAIL PROTECTED] wrote:
I hope you are using svn2.freepascal.org for these test, as not to
disturb the production use on svn.freepascal.org.
It is now, thanks...
Regards,
- Graeme -
___
fpGUI - a cross-platform
Graeme Geldenhuys schrieb:
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
Git is a hype. Git might be nice for projects with 100 developers and
which has (like linux) dedicated branch maintainers. Git allows to
support complicated project structures with several layers of
On Wed, Nov 5, 2008 at 22:15, Graeme Geldenhuys [EMAIL PROTECTED] wrote:
Once the full history Git checkout is complete, I'll compress it with
7zip as well to see how small it can go.
Git already has efficient repository packing (try git repack -a -d).
I doubt you gain anything by applying
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
No. The point is that a dvcs has drawbacks. The distributed nature
requires a very strict management of repository structure and for the
changeset flow.
You have the exact same issues with SubVersion!
Which repository is used the create
See my other mail ;)
Please watch the YouTube demo on Git. You will find it enlighening -
I'm busy watching it now. The guy doing the demo has only used Git in
small teams 3-6 developers and admits he hasn't used in in large
environments (like Linux kernel), yet he is still impressed by the
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
the more complex use of a dvcs. Here at work I'am happy if people use
svn up/svn co correctly and not do svn rm/svn add to commit a changed file.
With subversion is this self regulated and the structure subversion
offers is enough for
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
Graeme Geldenhuys schrieb:
For the record, the whole lazarus svn repository on idefix is 392 MB,
i.e. including all history.
What is idefix?
Like I mentioned before... I did a fresh Lazarus Trunk (head) revision
checkout with svn. The
Graeme Geldenhuys schrieb:
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
Graeme Geldenhuys schrieb:
For the record, the whole lazarus svn repository on idefix is 392 MB,
i.e. including all history.
What is idefix?
The machine running svn.freepascal.org.
Like I mentioned
Graeme Geldenhuys schrieb:
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
the more complex use of a dvcs. Here at work I'am happy if people use
svn up/svn co correctly and not do svn rm/svn add to commit a changed file.
With subversion is this self regulated and the structure
2008/11/5 Florian Klaempfl [EMAIL PROTECTED]:
Graeme Geldenhuys schrieb:
And to use branches I need write access to the SVN repository. So now
you will be happy giving everybody write access?
People having asked so far, got their own branch, at least for FPC.
And filling the
'branches'
Vincent Snijders schrieb:
2008/11/5 Florian Klaempfl [EMAIL PROTECTED]:
Graeme Geldenhuys schrieb:
And to use branches I need write access to the SVN repository. So now
you will be happy giving everybody write access?
People having asked so far, got their own branch, at least for FPC.
And
On Wed, Nov 05, 2008 at 02:20:10PM +0100, Florian Klaempfl wrote:
Graeme Geldenhuys schrieb:
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
the more complex use of a dvcs. Here at work I'am happy if people use
svn up/svn co correctly and not do svn rm/svn add to commit a changed
On Wed, Nov 5, 2008 at 3:20 PM, Florian Klaempfl [EMAIL PROTECTED] wrote:
The better way is imo to create a branch at the main repository where
you can work, so as I said in my other mail, it is backed up, everybody
can review it early and easily,
My last point on the subject... You last
On 11/5/08, Florian Klaempfl [EMAIL PROTECTED] wrote:
Git for our company repositories. In SubVersion, branching is like an
afterthought. Manually having to track merges to a branch (though
apparently there was been some work towards this), etc...
This is not true. svnmerge works very
30 matches
Mail list logo
