Southern California, Los Angeles, CA 90089 USA
++
-Original Message-
From: jpluser
Reply-To: "dev@tika.apache.org"
Date: Friday, January 1, 2016 at 8:30 PM
To: "dev@tika.apache.org"
Subject: [VOTE] Mo
+1
On 2 January 2016 at 04:30, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:
> Hi Everyone,
>
> DISCUSS thread here: http://s.apache.org/wVE
>
> Time to officially VOTE on moving Tika to Git. I’ve made a wiki
> page for our SCM explaining how to use Git at Apache, and how to
>
Hi.
[x] +1 Move the Apache Tika source control to Writeable Git repos
at the ASF
[ ] +0 Indifferent.
[ ] -1 Don’t move the Apache Tika source control to Writeable Git
repos at the ASF because..
For me git is more convenient (and I actually use git-svn for svn repos).
пн, 11 янв. 2016 г. в 19:32,
On 02/01/16 04:30, Mattmann, Chris A (3980) wrote:
Hi Everyone,
DISCUSS thread here: http://s.apache.org/wVE
Time to officially VOTE on moving Tika to Git. I’ve made a wiki
page for our SCM explaining how to use Git at Apache, and how to
use it with Github, and how to use it even in a tradition
+1
-- Ken
> From: Mattmann, Chris A (3980)
> Sent: January 1, 2016 8:30:16pm PST
> To: dev@tika.apache.org
> Subject: [VOTE] Moving SCM to Git
>
> Hi Everyone,
>
> DISCUSS thread here: http://s.apache.org/wVE
>
> Time to officially VOTE on moving Tika to Git. I
+1
Thank you, Chris, for moving forward on this!
-Original Message-
From: Mattmann, Chris A (3980) [mailto:chris.a.mattm...@jpl.nasa.gov]
Sent: Friday, January 01, 2016 11:30 PM
To: dev@tika.apache.org
Subject: [VOTE] Moving SCM to Git
Hi Everyone,
DISCUSS thread here: http
[X] +1 Move the Apache Tika source control to Writeable Git repos
at the ASF
On Sat, Jan 2, 2016 at 7:40 PM, wrote:
>
>
> DISCUSS thread here: http://s.apache.org/wVE
>
> Time to officially VOTE on moving Tika to Git. I’ve made a wiki
> page for our SCM explaining how to use Git at Apache, and h
ements. svn
> inherently has the first nailed, and is much easier for provenance (there
> may be edge cases I'm missing offhand, but we know the ICLA/grant
> associated with each change leading up to the tagged release).
> >>
> >> Did it wind up as "projects can
may be edge
>>> cases I'm missing offhand, but we know the ICLA/grant associated with each
>>> change leading up to the tagged release).
>>
>> Did it wind up as "projects can experiment with using git for official
>> releases"?
>>
>
d is much easier for provenance (there may be edge cases I'm
>> missing offhand, but we know the ICLA/grant associated with each change
>> leading up to the tagged release).
>
> Did it wind up as "projects can experiment with using git for official
> releases&
h using git for official
releases"?
Thanks,
-- Ken
> From: Mattmann, Chris A (3980)
> Sent: January 1, 2016 8:30:16pm PST
> To: dev@tika.apache.org
> Subject: [VOTE] Moving SCM to Git
>
> Hi Everyone,
>
> DISCUSS thread here: http://s.apache.org/wVE
>
> Time t
Hi Everyone,
DISCUSS thread here: http://s.apache.org/wVE
Time to officially VOTE on moving Tika to Git. I’ve made a wiki
page for our SCM explaining how to use Git at Apache, and how to
use it with Github, and how to use it even in a traditional SVN
sense. The page is here:
https://wiki.apache.
12 matches
Mail list logo