Nachricht-
Von: Antoine Levy Lambert [mailto:anto...@gmx.de]
Gesendet: Mittwoch, 7. Mai 2014 02:18
An: Ant Developers List
Betreff: Re: Hoped for advantages of migrating to git
Matt, Jesse,
I think that both of you are basically saying that accepting pull
requests entered in github is going
On 2014-05-07, Matt Sicker wrote:
The Camel project takes PRs from GH, though, so they may have some useful
info about that.
http://camel.apache.org/contributing.html#Contributing-PullrequestatGithub
sounds like manually merging the PR to the ASF git repo.
Stefan
. Mai 2014 02:18
An: Ant Developers List
Betreff: Re: Hoped for advantages of migrating to git
Matt, Jesse,
I think that both of you are basically saying that accepting pull
requests entered in github is going to be more manual work, including
more command line work, in the case
Developers List
Betreff: Re: Hoped for advantages of migrating to git
Matt, Jesse,
I think that both of you are basically saying that accepting pull
requests entered in github is going to be more manual work, including
more command line work, in the case of a migration to git-wip
?)
Jan
-Ursprüngliche Nachricht-
Von: Antoine Levy Lambert [mailto:anto...@gmx.de]
Gesendet: Mittwoch, 7. Mai 2014 02:18
An: Ant Developers List
Betreff: Re: Hoped for advantages of migrating to git
Matt, Jesse,
I think that both of you are basically saying that accepting
I added my GH account info a while ago, but it only added my account to the
ASF organization on GH. It's kinda buggy with linking histories even, and
INFRA isn't too interested in resolving those issues since it's outside ASF.
The Camel project takes PRs from GH, though, so they may have some
On 2014-05-07, Antoine Levy Lambert wrote:
I don’t know whether an option of using only github and not the ASF
hosted git is acceptable for the ASF ? for the Ant committers ?
For the ASF the only thing that matters is that the ASF git instance is
the source of truth. Tags are there and the
On 2014-05-06, Matt Sicker wrote:
Git allows you to do both. You can auto-merge from GH, but I'm not
sure how you can even get write access to ASF GH repos.
You don't, you commit to the ASF repo and it gets mirrored.
IIRC some projects have their own forks of the ASF mirror and accept
pull
I mean how do you accept pull requests? You wouldn't be able to do it
through GitHub. You'd have to manually pull the branch from GitHub like the
name pull request implies. If you could commit to GitHub, then you could
add a remote besides origin for GitHub, then pull from the GitHub remote,
then
Matt, Jesse,
I think that both of you are basically saying that accepting pull requests
entered in github is going to be more manual work,
including more command line work, in the case of a migration to
git-wip-us.apache.org as opposed to migrating to use only github.
I don’t know whether an
using
git for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert
anto...@gmx.de
wrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone an original repository
On Mon, May 5, 2014 at 8:22 AM, Nicolas Lalevée
nicolas.lale...@hibnet.org wrote:
once a committer is satisfied with the result, the work is being imported
into the git repo with a script
A much more straightforward workflow is just to do all work in the
GitHub repo, accepting pull requests
Git allows you to do both. You can auto-merge from GH, but I'm not sure how
you can even get write access to ASF GH repos.
On Monday, 5 May 2014, Jesse Glick typr...@gmail.com wrote:
On Mon, May 5, 2014 at 8:22 AM, Nicolas Lalevée
nicolas.lale...@hibnet.org javascript:; wrote:
once a
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone an original repository and in fact to
create a fork while keeping the possibility of contributing back what they have
created if they want to, and also
If you don't mind some recommendations from the peanut gallery (been using
git for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert anto...@gmx.dewrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git
git for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert anto...@gmx.de
wrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone an original repository and in fact
recommendations from the peanut gallery (been using
git for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert anto...@gmx.dewrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone
:
If you don't mind some recommendations from the peanut gallery (been using
git for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert anto...@gmx.dewrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git
Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone an original repository and in fact
to
create a fork while keeping the possibility of contributing back what
they
have created if they want
git for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert anto...@gmx.de
wrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone an original repository and in fact
for 5 years now)
On Wed, Apr 30, 2014 at 9:53 AM, Antoine Levy-Lambert
anto...@gmx.de
wrote:
Hello Maarten,
I do not know a lot about git either.
Here are the advantages I see in migrating to git :
- git allows third-parties to clone an original repository and in
fact
Le 20 avr. 2014 à 17:34, Antoine Levy Lambert anto...@gmx.de a écrit :
Hi,
like Michael one of my hopes in migrating to git is that it will allow non
ASF committers
to create their own forks of projects and be able to keep them (or not) up to
date with the
master branch.
I have
OR pull
http://gitref.org/remotes/#fetch
(you can then resync with remote repo when WIFI access is restored)
HTH
Martin
__
From: apa...@materne.de
To: dev@ant.apache.org
Subject: AW: Migrating to Git
Date: Mon, 14 Apr 2014 14:42:59
Hi,
like Michael one of my hopes in migrating to git is that it will allow non ASF
committers
to create their own forks of projects and be able to keep them (or not) up to
date with the
master branch.
I have also done a little bit of investigation to see how other projects have
migrated
HI there,
Since write git repository are accessible for a while, i suggest (as many
of you) to switch projects to git.
I know this has been discussed many times [1] but never in a dedicated
thread.
So what do you think about this ?
Are you ok to migrate :
* ant
* ivy / ivyde
* easyant
*
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
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
On Apr 14, 2014, at 7:17 AM, Stefan Bodewig bode...@apache.org 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
2014-04-14 11:59 GMT+02:00 Nicolas Lalevée nicolas.lale...@hibnet.org:
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
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.
Camel
: Migrating to Git
Date: Mon, 14 Apr 2014 14:42:59 +0200
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
I'm happy with Subversion, so for me there is no need to switch to git.
Maarten
Van: Jean-Louis Boudart jeanlouis.boud...@gmail.com
Aan: Ant Developers List dev@ant.apache.org
Verzonden: maandag 14 april 8:24 2014
Onderwerp: Migrating to Git
HI
32 matches
Mail list logo
