Hey, no worries. I don't have the spare cycles to work on the M2
migration myself, so whatever method you guys think is best, I'm all
for it. I just wanted to make sure you're prepared for some pain down
the road if you go the branch path, beacuse I think it will be nasty.
If I were doing this
Jacek Laskowski wrote:
On 7/5/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
I'm afraid that I have to agree w/ Aaron here Jacek. I'm not sure that
there was a consensus on this. If discussion died down on this it was
because it's the 4th of July.
Ok, you *might* be right, but should I vote
On 7/5/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
I'm afraid that I have to agree w/ Aaron here Jacek. I'm not sure that
there was a consensus on this. If discussion died down on this it was
because it's the 4th of July.
Ok, you *might* be right, but should I vote for creating a branch f
Jacek Laskowski wrote:
On 7/4/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
When discussing whether a branch was appropriate, I expressed a
concern that it would be difficult to merge changes from this branch
to HEAD because SVN seems to have difficulty handling multiple
revisions of add/delete/m
On 7/4/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
When discussing whether a branch was appropriate, I expressed a
concern that it would be difficult to merge changes from this branch
to HEAD because SVN seems to have difficulty handling multiple
revisions of add/delete/move/copy operations in a
Jason,
INAL, but sections 10 B-E in their open source contract don't sound
appropriate for ASF use to me.
http://www.perforce.com/perforce/contracts/open_source.pdf
We wouldn't want the situation where we have to uninstall it or Apache
and the development community has to start paying for it
On Jul 4, 2006, at 4:21 AM, Aaron Mulder wrote:
Are you recommending that the project switch to Perforce, or is this
just wishful thinking?
Well... both I guess. But given our reality its more of the later.
Also, one more note on the merging -- If we change the directory
layout in the branc
Sent a note in a related thread asking to have RTC suspended for this activity and let the work
proceed in trunk directly.
Aaron Mulder wrote:
Are you recommending that the project switch to Perforce, or is this
just wishful thinking?
Also, one more note on the merging -- If we change the dire
Are you recommending that the project switch to Perforce, or is this
just wishful thinking?
Also, one more note on the merging -- If we change the directory
layout in the branch, it will be very hard to merge any patches to
HEAD into the branch to keep them in sync since all the patch paths
will
FYI... Perforce may be commercial, but they provide free licenses for
qualifying open source usage:
http://perforce.com/perforce/opensource-faq.html
:-)
--jason
On Jul 4, 2006, at 3:50 AM, Aaron Mulder wrote:
Jacek,
When discussing whether a branch was appropriate, I expressed a
conc
Jacek,
When discussing whether a branch was appropriate, I expressed a
concern that it would be difficult to merge changes from this branch
to HEAD because SVN seems to have difficulty handling multiple
revisions of add/delete/move/copy operations in a single merge (and I
understand the M2 restru
Hi,
Just created a branch - m2migration - for all our work pertaining to
the M2 migration of Geronimo build. Everybody's welcome to work on it
*without* RTC on. Revolutionary rules are enabled again! ;-)
The branch is available at
https://svn.apache.org/repos/asf/geronimo/branches/m2migration.
12 matches
Mail list logo
