lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noble Paul നോബിള്‍ नोब्ळ् <noble.p...@gmail.com>
Subject Re: The Old Git Discussion
Date Fri, 03 Jan 2014 15:57:42 GMT
I personally have -0

I don't have any preference. Minus because it would change my comfortable
workflow. Is there any pressing need to switch? Or, if someone has to give
one real reason for the switch, what would it be ?
On 3 Jan 2014 20:49, "Mark Miller" <markrmiller@gmail.com> wrote:

> Just to answer some of your questions:
>
> On Jan 3, 2014, at 8:18 AM, Uwe Schindler <uwe@thetaphi.de> wrote:
>
> > Hi,
> >
> > I fully agree with Robert: I don't want to move to GIT. In addition,
> unless there is some tool that works as good as Windows' TortoiseSVN also
> for GIT, so I can merge in milliseconds(TM), I won't commit anything.
>
> SmartGit is way better than TortoiseSVN IMO. Your favorite tool is a silly
> way to decide something like this IMO as well though.
>
> >
> > I just note: I was working as committer for the PHP project (maintaining
> the SAPI module for Oracle iPlanet Webserver), but since they moved to GIT
> 2 years ago, I never contributed anything anymore. I just don't understand
> how it works and its completely unusable to me. E.g. look at this bullshit:
> https://wiki.php.net/vcs/gitworkflow - Sorry this is a no-go. And I have
> no idea what all these cryptic commands mean and I don't want to learn
> that. If we move to GIT, somebody else have to commit my patches.
>
> Others committed your patches in the past and I’m sure they will continue
> to do so in the future if you desire.
>
> >
> > And the other comment that was given here is not true: Merging with SVN
> works perfectly fine and is easy to do, unless you use the command line or
> Eclipse's bullshit SVN client (that never works correctly). With a good GUI
> (like the fantastic TortoiseSVN), merging is so simple and conflicts can be
> processed in milliseconds(TM). And it is much easier to understand.
>
> An opinion not commonly shared by my reading. At a minimum, simply opinion
> though.
>
> >
> > Also Subversion is an Apache Project and I want to add: We should eat
> our own dog food. Just to move to something with a crazy license and a
> broken user interface, just because it's cool, is a no-go to me.
>
> Certainly not because it’s cool! Who argued that?
>
> > We would also need to rewrite all our checking tasks (like the
> check-svn-working-copy ANT task) to work with GIT. Is there a pure Java
> library that works for GIT? I assume: No.
>
> You assume wrong. JGit is used by many projects, I’ve used it myself.
>
> > So this is another no-go for me. The checks we do cannot be done by
> command line.
>
> I guess it’s not a no go then, because your assumption was wrong…
>
> - Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>

Mime
View raw message