I'm happy with Subversion, so for me there is no need to switch to git.
Maarten
Van: Jean-Louis Boudart
Aan: Ant Developers List
Verzonden: maandag 14 april 8:24 2014
Onderwerp: Migrating to Git
HI there,
Since write git repository are accessible for a w
Jan/Stefan
This is the license.txt which sits in every apache project
Maven currently contains license in $M2_HOME/license.txt
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS A
> > And I have not searched in the ASF docs, but do you have any pointer
> > on some guidelines about handling IP ? Can we merge any pull request
> >
> Don't have any pointer about handling IP but i'm sure people invested
> in other Apache project present in this ML could give us their
> guidelines
2014-04-14 11:59 GMT+02:00 Nicolas Lalevée :
> I like git, so I like the idea.
>
> But what about the publication of the doc on the website ? Today we rely
> on svn:externals for the doc of each release. How would it be managed if
> it's migrated to git ?
>
I think this could be solved with git su
On Apr 14, 2014, at 7:17 AM, Stefan Bodewig wrote:
> On 2014-04-14, Nicolas Lalevée wrote:
>
>> But what about the publication of the doc on the website ? Today we
>> rely on svn:externals for the doc of each release. How would it be
>> managed if it's migrated to git ?
>
> We'd likely need to
On 2014-04-14, Nicolas Lalevée wrote:
> But what about the publication of the doc on the website ? Today we
> rely on svn:externals for the doc of each release. How would it be
> managed if it's migrated to git ?
We'd likely need to copy stuff around. TBH I'm not too sure we're still
using exter
I like git, so I like the idea.
But what about the publication of the doc on the website ? Today we rely on
svn:externals for the doc of each release. How would it be managed if it's
migrated to git ?
And I have not searched in the ASF docs, but do you have any pointer on some
guidelines about
