On Wed, 10 Sep 2014 07:49:13 +0300, Silviu Burcea wrote:
This is the killer feature for Git, because many of us, the
newcomers, like
me, will want to experiment a little before submitting a patch. This
way, I
can create a local branch and I'm free to do whatever I want. The SVN
branch is visible on the server, I don't want to publish my crappy
code
before I feel that the feature or the bugfix has high quality and is
readable enough.
This use case does not convince me at all: when working on a feature,
you always do it locally (modifying code, preparing unit tests), and
SVN certainly does not force you to experiment publicly; it's rather
the project's policy that forbids you to commit crappy code. :-)
[The advantages of "git" must be somewhere else.]
Regards,
Gilles
Regards,
Silviu
On Tue, Sep 9, 2014 at 9:12 PM, Mark Fortner <phidia...@gmail.com>
wrote:
Paul,
Git branching is faster, computationally cheaper, and requires less
disk
space than svn branching. This link provides more information:
https://git.wiki.kernel.org/index.php/GitSvnComparison.
In git, you have a remote repo, and a local repo. Typically, people
create
local branches for experiments or new features and then merge and
create
pull-requests whenever they have something that they want to share
with the
community. In svn, whenever you branch, you're branching on the
server
first. Usually, if you're new to a code base, you don't want to do
that if
you're just experimenting. Ideally, you want to encourage
experimentation
(and attract new developers), so "feature branches" make a lot of
sense in
that context.
Cheers,
Mark
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
