Hello!
I thought to share [1] since some of you are 'interested' in git;
The #CouchDB guys are now on git, at the ASF!
Cheers!
Matthias
[1] http://git-wip-us.apache.org/repos/asf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net
Am 10/7/11 9:04 PM, schrieb Matthias Wessendorf:
Hello!
I thought to share [1] since some of you are 'interested' in git;
The #CouchDB guys are now on git, at the ASF!
Cheers!
Matthias
[1] http://git-wip-us.apache.org/repos/asf
Git support is still beta but nevertheless this is good news
+1
On Thu, Jul 9, 2009 at 12:20 AM, Manfred Geilermanfred.gei...@gmail.com wrote:
+1
thanks leonardo
--Manfred
On Thu, Jul 9, 2009 at 04:24, Leonardo Uribelu4...@gmail.com wrote:
Hi
Myfaces core 1.2.7 and 1.1.7 were released. So we can close this vote and
make the necessary changes. Just
+1
thanks leonardo
--Manfred
On Thu, Jul 9, 2009 at 04:24, Leonardo Uribelu4...@gmail.com wrote:
Hi
Myfaces core 1.2.7 and 1.1.7 were released. So we can close this vote and
make the necessary changes. Just to note it, after reading all previous
emails the suggested layout is this:
/trunk
Hi
Myfaces core 1.2.7 and 1.1.7 were released. So we can close this vote and
make the necessary changes. Just to note it, after reading all previous
emails the suggested layout is this:
/trunk - 2.0
/branches/1.1.x
/branches/1.2.x
If no objections I'll do the necessary changes on svn (note that
that would be great ! Thx Leo!
-Matthias
On Thu, Jul 9, 2009 at 4:24 AM, Leonardo Uribelu4...@gmail.com wrote:
Hi
Myfaces core 1.2.7 and 1.1.7 were released. So we can close this vote and
make the necessary changes. Just to note it, after reading all previous
emails the suggested layout is
sure!
On Thu, May 28, 2009 at 6:34 AM, Leonardo Uribe lu4...@gmail.com wrote:
+1, but just a small suggestion. Right now I'm running the necessary steps
for release myfaces core 1.2.7, core 1.1.7, so I would like if it is
possible to delay this change after the release.
regards
Leonardo
+1
On Thu, May 28, 2009 at 2:23 AM, Matthias Wessendorf mat...@apache.orgwrote:
sure!
On Thu, May 28, 2009 at 6:34 AM, Leonardo Uribe lu4...@gmail.com wrote:
+1, but just a small suggestion. Right now I'm running the necessary
steps
for release myfaces core 1.2.7, core 1.1.7, so I would
so, there are no objections in making the MyFaces 2.0 efforts become trunk ?
-Matthias
On Fri, May 22, 2009 at 9:10 PM, Bernd Bohmann
bernd.bohm...@atanion.com wrote:
Hello,
+1
I would prefer
/trunk - 2.0
/branches/myfaces-1.1.x
/branches/myfaces-1.2.x
because we are not using cvs
+1 sounds good to me
2009/5/27 Matthias Wessendorf mat...@apache.org:
so, there are no objections in making the MyFaces 2.0 efforts become trunk ?
-Matthias
On Fri, May 22, 2009 at 9:10 PM, Bernd Bohmann
bernd.bohm...@atanion.com wrote:
Hello,
+1
I would prefer
/trunk - 2.0
+1 for sure
On Wed, May 27, 2009 at 8:53 AM, Bruno Aranda brunoara...@gmail.com wrote:
+1 sounds good to me
2009/5/27 Matthias Wessendorf mat...@apache.org:
so, there are no objections in making the MyFaces 2.0 efforts become
trunk ?
-Matthias
On Fri, May 22, 2009 at 9:10 PM, Bernd
+1, but just a small suggestion. Right now I'm running the necessary steps
for release myfaces core 1.2.7, core 1.1.7, so I would like if it is
possible to delay this change after the release.
regards
Leonardo Uribe
2009/5/27 Cagatay Civici cagatay.civ...@gmail.com
+1 for sure
On Wed, May
Ah. Good point!
Sent from my iPod.
On 22.05.2009, at 21:10, Bernd Bohmann bernd.bohm...@atanion.com
wrote:
Hello,
+1
I would prefer
/trunk - 2.0
/branches/myfaces-1.1.x
/branches/myfaces-1.2.x
because we are not using cvs anymore
and the path already contains
actually, I agree with Bernd.
For the following layout:
/trunk - 2.0
/branches/myfaces_1_1_x
/branches/myfaces_1_2_x
Two reasons for way making 2.0 trunk:
-most current development is on-going in 2.0 (new spec)
-most commits are going to the 2.0 branch (so, let's make it trunk)
So, I am +1 on
Hello,
+1
I would prefer
/trunk - 2.0
/branches/myfaces-1.1.x
/branches/myfaces-1.2.x
because we are not using cvs anymore
and the path already contains
http://svn.apache.org/repos/asf/myfaces/core/
maybe we can omit the 'myfaces' in the branch name.
Regards
Bernd
On Fri, May 22, 2009
On Sat, May 16, 2009 at 7:41 AM, Werner Punz werner.p...@gmail.com wrote:
Ah lovely saturday morning and a general technology discussion.
Ok here is the deal, it is a very common practice to use git for local
versioning and svn or cvs for hosting the code (I do that very often). There
are
Hello,
I would suggest following layout
1.1.x branch/1.1.x
1.2.x branch/1.2.x
2.0.x trunk
because the 2.0.x version is in development the other branches are
only in bugfix state.
Regards
Bernd
On Fri, May 15, 2009 at 11:39 AM, Matthias Wessendorf mat...@apache.org wrote:
On Fri, May 15,
from Bernd, on a different thread:
Hello,
I would suggest following layout
1.1.x branch/1.1.x
1.2.x branch/1.2.x
2.0.x trunk
because the 2.0.x version is in development the other branches are
only in bugfix state.
On Fri, May 15, 2009 at 1:13 PM, Werner Punz werner.p...@gmail.com wrote:
Ok before I make myself a complete idiot...
(Which I probably will be doing now)
There are a load of errata in my previous post, more than the usual
answering while doing other things and also being a completely chaotic
personality, induced errors.
I answered shortly after waking up and
Matthias Wessendorf schrieb:
Werner,
according to here:
http://www.apache.org/dev/git.html
we need to provide the following information, for the INFRA jira ticket:
* Name of the codebase, for example Apache Tika
* Name of the requested Git mirror, for example tika.git
* Subversion
Matthias Wessendorf schrieb:
core
Ok, I filed this:
https://issues.apache.org/jira/browse/INFRA-2053
maybe we should also think about making the JSF 1.1.x stuff a branch ...
(since we already work on 2.0.x)
+1
1.1.x branch
1.2 trunk
2.0 branch
instead of
1.1 trunk
1.2 trunk_1.2
2.0
Hi,
...
Ok, I filed this:
https://issues.apache.org/jira/browse/INFRA-2053
maybe we should also think about making the JSF 1.1.x stuff a branch ...
(since we already work on 2.0.x)
what do people think if the 1.2 stuff becomes trunk
And the following efforts are on a branch:
-2.0.x
On Fri, May 15, 2009 at 11:37 AM, Werner Punz werner.p...@gmail.com wrote:
Matthias Wessendorf schrieb:
core
Ok, I filed this:
https://issues.apache.org/jira/browse/INFRA-2053
maybe we should also think about making the JSF 1.1.x stuff a branch ...
(since we already work on 2.0.x)
+1
Matthias Wessendorf schrieb:
Hi,
...
Ok, I filed this:
https://issues.apache.org/jira/browse/INFRA-2053
maybe we should also think about making the JSF 1.1.x stuff a branch ...
(since we already work on 2.0.x)
what do people think if the 1.2 stuff becomes trunk
And the following efforts
some more infos:
http://wiki.apache.org/general/GitAtApache
On Fri, May 15, 2009 at 11:39 AM, Matthias Wessendorf mat...@apache.org wrote:
On Fri, May 15, 2009 at 11:37 AM, Werner Punz werner.p...@gmail.com wrote:
Matthias Wessendorf schrieb:
core
Ok, I filed this:
I would say -1. Seems pointless to use another version control client
that is not 100% compatible with SVN when the SVN command-line and UI
clients works fine. What next, a mercurial read-only repository too?
We have chosen to use subversion with MyFaces at Apache, I don't see
any reason to
I don't know much about git, but I know that other committers on
Apache Cayenne use git to commit to the Cayenne svn, so it's certainly
possible to do what Andrew suggests. From my limited git
understanding, that's the typical practice of using git -- as a
front-end to svn or cvs.
On Fri, May
Hey andrew,
Thanks for your mail. There is a discussion on the members list. Let
me point them to our thread.
Thanks again!
Sent from my iPod.
On 15.05.2009, at 22:08, Andrew Robinson
andrew.rw.robin...@gmail.com wrote:
I would say -1. Seems pointless to use another version control
Anderw, I asked to move the thread to committ...@.
Thx
Matthias
Sent from my iPod.
On 15.05.2009, at 22:21, Matthias Wessendorf mwessend...@gmail.com
wrote:
Hey andrew,
Thanks for your mail. There is a discussion on the members list. Let
me point them to our thread.
Thanks again!
Ah lovely saturday morning and a general technology discussion.
Ok here is the deal, it is a very common practice to use git for local
versioning and svn or cvs for hosting the code (I do that very often).
There are downsides to this practice. First of all git-svn does not have
external
On Tue, Apr 28, 2009 at 12:14 PM, Werner Punz werner.p...@gmail.com wrote:
Matthias Wessendorf schrieb:
Hi fellow contributors and committers,
a recently common asked question is:
Is it possible for an ASF project (- myfaces and its subprojects) to
use git ?
The answer is:
Yes and no.
Werner,
according to here:
http://www.apache.org/dev/git.html
we need to provide the following information, for the INFRA jira ticket:
* Name of the codebase, for example Apache Tika
* Name of the requested Git mirror, for example tika.git
* Subversion path of the codebase, for
Matthias Wessendorf schrieb:
Hi fellow contributors and committers,
a recently common asked question is:
Is it possible for an ASF project (- myfaces and its subprojects) to
use git ?
The answer is:
Yes and no. All projects need to use svn as the central store of all
source code, but
Matthias Wessendorf schrieb:
Hi fellow contributors and committers,
a recently common asked question is:
Is it possible for an ASF project (- myfaces and its subprojects) to
use git ?
The answer is:
Yes and no. All projects need to use svn as the central store of all
source code, but
Hi fellow contributors and committers,
a recently common asked question is:
Is it possible for an ASF project (- myfaces and its subprojects) to
use git ?
The answer is:
Yes and no. All projects need to use svn as the central store of all
source code, but individual committers and contributors
35 matches
Mail list logo
