ut have only gathered some initial Git resources
> so far.
>
> I'm finishing a sprint this week and next and then I'm off sprint for a
> couple of weeks, I plan on expanding the page with the instructional
> portions during my holiday break, I've already got some things t
x27;ve already got some things to review
and some initial notes written down.
As far as the move to Git itself I'm pretty sure Carlos Rovira started a
JIRA issue, I'll double check it and post a link to this thread in a while.
-omar
HI,
Been any progress on this? I seem to recall that someone was working on a wiki
page with some instructions on how the git workflow will work.
While looking for something else I came across this - which may be of interest.
https://issues.apache.org/jira/browse/INFRA-5111
Kafta recently beca
A little late to the discussion but a great article on why you should
switch to git (from subversion) with a brief overview of Git,
http://teamtreehouse.com/blog/why-you-should-switch-from-subversion-to-git
On Tue, Aug 14, 2012 at 1:02 PM, Carol Frampton wrote:
>
>
> On 8/14/12 11 :58AM, "Carlo
But...if Git wasn't an option now Alex would not be listing it, isn't
it?...so If you think Git is the solution, IMHO is you should vote what you
think, because, as I said, is a valid option. If GIT ends as the preferred
solution (and there's many votes to option 9), we should go with GIT as
many o
>Then if even people like you that would vote for GIT in first instance, ends
>voting for the opposite...I think we are not doing us a favor.
Carlos,
Just to be clear. I didn't vote for Git in the first place. I said we should
consider it and I still think we should. I voted the way I did as I
On 8/14/12 6:47 AM, "João Fernandes"
wrote:
>
> Is there any pitfall for using GIT mirroring the SVN repository and having
> people commiting in both SVN/GIT?
>
The information I read is that you have to be very careful about how you use
Git if you plan to commit back via Git-SVN because it
On 8/14/12 11 :58AM, "Carlos Rovira" wrote:
>>
>> I think the conversation and relative merits is exactly what we should
>>be
>> doing. The only thing I wish is that, like other areas of the project,
>>we
>> didn't have to wait on someone else. If we could just demonstrate the
>> advantages of
Guys concentrate on that matters, voting!
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Tue, Aug 14, 2012 at 12:58 PM, Carlos Rovira <
carlos.rov...@codeoscopic.com> wrote:
> >
> > I think the conversation and relative merits is exactly what we should be
> > doi
>
> I think the conversation and relative merits is exactly what we should be
> doing. The only thing I wish is that, like other areas of the project, we
> didn't have to wait on someone else. If we could just demonstrate the
> advantages of Git instead of talking about them in the abstract, I thin
>> In my view, we still seem like a disparate group of individuals who
>> are most comfortable working alone or on small groups with great
>> amounts of autonomy. We are not a team yet & our Flex project isn't
>> self-sustaining.
>> My evidence is this conversation debating the relative merits o
On Tuesday, August 14, 2012, Guthmann, Scott wrote:
> > I'm not assuming we'll moving to GIT right away but as Bertrand
> mentioned, we need to work as a team and if PPMC members aren't able to
> find a strategy for Apache Flex when it comes to source control, how is it
> going to work for code ad
> I'm not assuming we'll moving to GIT right away but as Bertrand mentioned, we
> need to work as a team and if PPMC members aren't able to find a strategy for
> Apache Flex when it comes to source control, how is it going to work for code
> additions/changes?
I think João is pointing out somet
Personaly I think the Git stuff is more easy than it seems by the amount of
mails we are sharing. But hope all this mails will serve for people to
learn more about a better SCM system.
My vote counts like yours, but if there's many non-binding votes point to
GIT and PPMCs vote for SVN but there's
Carlos, I just can speak for myself and my vote counts nothing
(non-binding) but I'm willing to learn anything that is required but my
question is, besides the branching model to adopt, how much work is
required to have everything working under GIT?
Can it be a working process while code can keep b
Hi Joao,
The problem is not if flex is bigger than other projects. Or if other
bigger projects were successful using SVN.
The problem is tha flex is mature and need some changes in the deep core
classes and we will need a robust and consistent way to branch, share, test
and merge, all without bre
ou want to support GIt, please vote in the sbiling thread! vote is
> open
> > now! :)
> >
> > 2012/8/14 jude
> >
> > > I'm comfortable with SVN too but support the move to Git / GitHub
> because
> > > it is an environment that makes work like this m
As I said in another thread, I never used GIT but I'm willing to try it but
I think first of all we need to pick which branching model we're going to
follow.
Is there any pitfall for using GIT mirroring the SVN repository and having
people commiting in both SVN/GIT?
While I've learned a bit about
ng thread! vote is open
> now! :)
>
> 2012/8/14 jude
>
> > I'm comfortable with SVN too but support the move to Git / GitHub because
> > it is an environment that makes work like this much more efficient.
> People
> > can easily fork the project, make a change a
If you want to support GIt, please vote in the sbiling thread! vote is open
now! :)
2012/8/14 jude
> I'm comfortable with SVN too but support the move to Git / GitHub because
> it is an environment that makes work like this much more efficient. People
> can easily fork the p
I'm comfortable with SVN too but support the move to Git / GitHub because
it is an environment that makes work like this much more efficient. People
can easily fork the project, make a change and get it to a working state.
Then the main branch can easily patch those changes back in. It is al
Igor, until now (flex < 4.8) I don' t see deep changes in flex core like
the ones people want to perform. Spark and other features were always
"additive".
SVN works well with such projects. But we target now other kind of changes
in the core that never was done before in flex.
So I would like to
On Mon, Aug 13, 2012 at 9:53 AM, Igor Costa wrote:
> Carlos
>
> "But the real problem for me is that we can't target the changes we plan
> without a tool like Git. Maybe people that does not know Git does not
> understand this, but we were not able to make such deep changes if we are
> using SVN.
Carlos
"But the real problem for me is that we can't target the changes we plan
without a tool like Git. Maybe people that does not know Git does not
understand this, but we were not able to make such deep changes if we are
using SVN."
Flex SDK was built over 4 versions using SVN, Since Flex 3 we
IMHO, and taking into account that I'm only a not-binding vote...
I don't see real arguments against Git and maybe as Omar says people does
not want to figth with yet another SCM...
But the real problem for me is that we can't target the changes we plan
without a tool like Git. Maybe people that
On Mon, Aug 13, 2012 at 9:26 AM, Carol Frampton wrote:
> A clarification question about Git:
>
> Would I lose the ability to look at the repro thru the web. I make use of
> https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more often then
> I expected.
>
> Carol
> >
>
>
You can browse it
A clarification question about Git:
Would I lose the ability to look at the repro thru the web. I make use of
https://svn.apache.org/repos/asf/incubator/flex/trunk/ etc more often then
I expected.
Carol
>
ertrand's emails last week to
>> reiterate his warning message [1]:
>>
>> Let me add one BIG WARNING as a mentor: branches might be much easier
>> to manage with Git, but if a move to Git is a way to avoid agreeing on
>> how branches are managed, that won't he
On Mon, Aug 13, 2012 at 6:13 PM, Omar Gonzalez
wrote:
> ...The way Apache (doesn't) supports Git kind of sucks anyhow, as it
> essentially leaves sVN as the primary and uses Git as an interface
> basically
No.
That's only one of the options, please read s.apache.org/flex_git_options
-Bertra
On Mon, Aug 13, 2012 at 10:50 AM, Alex Harui wrote:
> I think folks want to use Git as the main repo. But when I follow the
> instructions on [1] it isn't working. "git push" does not run successfully.
>
> Because it is "experimental", can we open Infra tickets or is this where we
> need to supp
t least 48 hours since I now have to drop
> everything I was working on to go learn enough about Git to vote.
>
> I would also like to paste from one of Bertrand's emails last week to
> reiterate his warning message [1]:
>
> Let me add one BIG WARNING as a mentor: branche
On Mon, Aug 13, 2012 at 5:50 PM, Alex Harui wrote:
> ...I think folks want to use Git as the main repo. But when I follow the
> instructions on [1] it isn't working. "git push" does not run successfully...
Those instructions won't work for Flex, as it does not have a writable
Git repository at
> IMHO, I do not accept for Git move right now.
> We must continue in SVN this means that projects keep going. Maybe when we
> have a solid proper release like 5.0 we should move to git.
I have to agree with Igor on this topic. I realize how much fun it is to debate
tools and differen
On 8/13/12 8:04 AM, "Bertrand Delacretaz" wrote:
>
> That's one of the options that I listed at
> http://s.apache.org/flex_git_options - the other one is to start using
> Git (on an apache.org server) as Flex's main code repository instead
> of svn. See my notes at http://s.apache.org/flex_g
to vote.
I would also like to paste from one of Bertrand's emails last week to
reiterate his warning message [1]:
Let me add one BIG WARNING as a mentor: branches might be much easier
to manage with Git, but if a move to Git is a way to avoid agreeing on
how branches are managed, that won'
Hi,
On Mon, Aug 13, 2012 at 4:51 PM, Alex Harui wrote:
> On 8/13/12 1:31 AM, "Bertrand Delacretaz" wrote:
>> ...See http://s.apache.org/flex_git_options...
>>
> ...I'm not sure how to interpret your response. That link points to your
> reply
> to Justin, but doesn't mention the wiki at all. D
IMHO, I do not accept for Git move right now.
We must continue in SVN this means that projects keep going. Maybe when we
have a solid proper release like 5.0 we should move to git.
Right now is a waste of time trying to procrastinating things that isn't
relevant to the project
On 8/13/12 1:31 AM, "Bertrand Delacretaz" wrote:
> On Mon, Aug 13, 2012 at 7:43 AM, Alex Harui wrote:
>> ...This is the page I was working from:
>> https://git-wip-us.apache.org/
>>
>> I'm not sure whether this document or the wiki document takes precedence...
>
> See http://s.apache.org/fl
On Mon, Aug 13, 2012 at 7:43 AM, Alex Harui wrote:
> ...This is the page I was working from:
> https://git-wip-us.apache.org/
>
> I'm not sure whether this document or the wiki document takes precedence...
See http://s.apache.org/flex_git_options
-Bertrand
On 8/12/12 1:11 AM, "Omar Gonzalez" wrote:
> I found some more info on Git at Apache.
>
> This link is meant for contributors that do not have committer access:
> http://www.apache.org/dev/git.html
>
> This link is meant for Apache committers:
> http://wiki.apache.org/general/GitAtApache
>
On Sunday, August 12, 2012, Greg Reddin wrote:
>
>
> Sent from my mobile device.
>
> On Aug 11, 2012, at 4:45 AM, Carlos Rovira
> >
> wrote:
>
> > When you want to plan a feature make a local branch to make your
> > development, better than start to make it directly on the initial branch.
> > Whe
Sent from my mobile device.
On Aug 11, 2012, at 4:45 AM, Carlos Rovira
wrote:
> When you want to plan a feature make a local branch to make your
> development, better than start to make it directly on the initial branch.
> When you finish, merge with final. You can as well publish your featu
HI,
> Well, you wouldn't be cherry picking from develop into master.
So everything in dev must work and be in a 100% working state in order to make
a release? That means we need to somehow veto changes in feature branches
before merging them with dev? So if we were to do this cheery picking peo
I found some more info on Git at Apache.
This link is meant for contributors that do not have committer access:
http://www.apache.org/dev/git.html
This link is meant for Apache committers:
http://wiki.apache.org/general/GitAtApache
Basically they're not opening up Git repositories to 'git push',
On Sun, Aug 12, 2012 at 12:24 AM, Justin Mclean wrote:
> Hi,
>
> > Why is using a local branch important?
> When using git most branches are local and not shared between developers
> unless it's needed (in my experience anyway). Although it easy to share
> between people working on a large feature
Hi,
> Why is using a local branch important?
When using git most branches are local and not shared between developers unless
it's needed (in my experience anyway). Although it easy to share between people
working on a large feature - have a look at the IDE dev on github and yuo'll
see that in a
On Sat, Aug 11, 2012 at 11:28 PM, Alex Harui wrote:
> Update: I am unable to commit. Can any other committer try to commit a
> change to some test file like SVN-TEST.txt?
>
> I got:
>
> "fatal: The remote end hung up unexpectedly"
>
> when trying to push to git://git.apache.org/flex.git and
What are the commands you are using?
On Sat, Aug 11, 2012 at 11:29 PM, Om wrote:
> I am on it.
>
> On Sat, Aug 11, 2012 at 11:28 PM, Alex Harui wrote:
>
>> Update: I am unable to commit. Can any other committer try to commit a
>> change to some test file like SVN-TEST.txt?
>>
>> I got:
>>
>>
I am on it.
On Sat, Aug 11, 2012 at 11:28 PM, Alex Harui wrote:
> Update: I am unable to commit. Can any other committer try to commit a
> change to some test file like SVN-TEST.txt?
>
> I got:
>
> "fatal: The remote end hung up unexpectedly"
>
> when trying to push to git://git.apache.org
Update: I am unable to commit. Can any other committer try to commit a
change to some test file like SVN-TEST.txt?
I got:
"fatal: The remote end hung up unexpectedly"
when trying to push to git://git.apache.org/flex.git and:
"fatal: https://git-wip-us.apache.org/repos/asf/flex.git/in
On Saturday, August 11, 2012, Alex Harui wro
>
>
>
>
> On 8/11/12 2:45 AM, "Carlos Rovira"
> >
> wrote:
>
> > Hi Alex,
> >
> > great to see you on Git now! :)
> >
> >
> > When you want to plan a feature make a local branch to make your
> > development, better than start to make it directly on the
On Sat, Aug 11, 2012 at 10:33 PM, Alex Harui wrote:
>
>
>
> On 8/11/12 2:45 AM, "Carlos Rovira" wrote:
>
> > Hi Alex,
> >
> > great to see you on Git now! :)
> >
> >
> > When you want to plan a feature make a local branch to make your
> > development, better than start to make it directly on the
On 8/11/12 2:45 AM, "Carlos Rovira" wrote:
> Hi Alex,
>
> great to see you on Git now! :)
>
>
> When you want to plan a feature make a local branch to make your
> development, better than start to make it directly on the initial branch.
Why is using a local branch important?
> When you fin
I'm with Omar,
it's like to point if people has computer to develop or not. It's up to
contributors to have the skills, time and needs required . The key point
here is the real needs for apache flex next iteration(s) and if SVN can
handle it or not. In my opinion is impossible to use SVN for what
I'm not saying everyone has DSL+.
I'm just saying connection speeds should not be considered for this
decision, sorry.
-omar
And we can't agree that all has DSL2+
Most people on world has 1Mb link shared connection with low latency.
That's why Apache has mirrors for each one of them.
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Sat, Aug 11, 2012 at 1:57 AM, Omar Gonzalez wrote:
Hi Alex,
great to see you on Git now! :)
First get a free Git client that will help you to get on track with this
new SCM. As we discussed before the best *free* clients are smart git on
windows and sourcetree on mac.
One thing to point now that you tried it is that philosophy behind Git is
litt
On 8/10/12 8:07 PM, "Omar Gonzalez" wrote:
>
> Went ahead and tried it myself also, here's my console log:
>
> quintessa:GitHub grimlock$ git clone git://git.apache.org/flex.git
> Cloning into 'flex'...
> remote: Counting objects: 330636, done.
> remote: Compressing objects: 100% (87765/8776
> the very first open source sdk revision
A blast from the past... I committed that!
Sent from my iPad
On Aug 10, 2012, at 7:22 PM, "Jeff Conrad" wrote:
> I went ahead and did it.
>
> I was able to clone the Apache Flex git repo both from github and
> git.apache.org. It was a 174 MB download
SourceTree is a great free one.
Shan
Sent from my iPhone
On Aug 10, 2012, at 11:28 PM, Justin Mclean wrote:
> Hi,
>
>> I don't use FB other than for editing. I use SmartSVN for SVN. I was
>> hoping GitHub for Mac would be the equivalent, but not so sure yet.
> The github client probably a bi
On Friday, August 10, 2012, Igor Costa wrote:
> [image: Inline image 1]
>
>
> With your such internet is pretty damn fast.
>
> With 56Kb/s transfer rate it take centuries. Specially for cloning.
>
>
> Of course will only happen first time when you clone it, than switch over
> branches are quite fa
Hi,
> I don't use FB other than for editing. I use SmartSVN for SVN. I was
> hoping GitHub for Mac would be the equivalent, but not so sure yet.
The github client probably a bit simpler. There are better graphical clients eg
Tower out there but I don't know of any good free/OS ones.
> The CLI
Hi,
I've used many VCS system over the years, RCS, PVCS, CVS, SNV, Clearcase,
Visual source safe and more recently Git and Mercurial.
Moving from Git from SVN is fairly easy but there's a few conceptual things
that are very different. I'd say it's the equivalent from going from a file
locking
[image: Inline image 1]
With your such internet is pretty damn fast.
With 56Kb/s transfer rate it take centuries. Specially for cloning.
Of course will only happen first time when you clone it, than switch over
branches are quite fast.
Igor Costa
www.igorcosta.
>
>
> On Fri, Aug 10, 2012 at 5:07 PM, Michael A. Labriola <
> labri...@digitalprimates.net> wrote:
>
> > >OK, but the first clone will be huge? I think our import file was in
> the
> > 10's of GBs. I'm afraid to try to clone the flex project over my home
> > network. I am testing by cloning the
On Friday, August 10, 2012, Alex Harui wrote:
>
>
> Anyway, I still am unable to find a way to clone from the Apache repo.
> GitHub seems to work, but I think that is read-only. If any committer can
> let me know how I can do that (and commit a test change) then I'll start a
> vote thread on movin
On Friday, August 10, 2012, Jeff Conrad wrote:
> I went ahead and did it.
>
> I was able to clone the Apache Flex git repo both from github and
> git.apache.org. It was a 174 MB download. I've done this multiple times
> over the last hour or so. I was able to clone it on Windows 7 using Git
> B
I went ahead and did it.
I was able to clone the Apache Flex git repo both from github and
git.apache.org. It was a 174 MB download. I've done this multiple times
over the last hour or so. I was able to clone it on Windows 7 using Git
Bash, inside Eclipse using the EGit plugin, and I even clone
To answer your questions:
1. Correct. Git is the technology, GitHub is a value-added service provider.
2. It's far easier than using SVN, but like most technologies, without a proper
plan in place, merging could get tricky.
Shan
On Aug 10, 2012, at 7:50 PM, Jeffry Houser wrote:
> On 8/10/2012
On 8/10/2012 6:37 PM, Igor Costa wrote:
As Carol, Gordon said, We must keep using SVN aside fact that is supported
by Apache Foundation.
Git is cool and is on stage now, but Flex has a HUGE source code base and
isn't easy to fork on github specially if you willing to download to your
machine.
Om,
Forking on github is fast, try to fork on your machine.
99% knows SVN based on answers gave in the thread.
Regards
Igor Costa
www.igorcosta.com
www.igorcosta.org
On Fri, Aug 10, 2012 at 7:53 PM, Om wrote:
> On Fri, Aug 10, 2012 at 3:37 PM, Igor Costa wrote:
>
On Fri, Aug 10, 2012 at 3:37 PM, Igor Costa wrote:
> As Carol, Gordon said, We must keep using SVN aside fact that is supported
> by Apache Foundation.
>
> Git is cool and is on stage now, but Flex has a HUGE source code base and
> isn't easy to fork on github specially if you willing to downloa
As Carol, Gordon said, We must keep using SVN aside fact that is supported
by Apache Foundation.
Git is cool and is on stage now, but Flex has a HUGE source code base and
isn't easy to fork on github specially if you willing to download to your
machine.
Likely getting truck carried by volks.
We
If you are on a Mac I strongly recommend source tree from attlasian. I
think is the better tool for git ever created. In windows I think smart git
is the option. My experience with egit was no so good.
El viernes, 10 de agosto de 2012, Michael A. Labriola escribió:
> >OK, but the first clone will
>OK, but the first clone will be huge? I think our import file was in the 10's
>of GBs. I'm afraid to try to clone the flex project over my home network. I
>am testing by cloning the flex-site which worked from github.
That is a big concern. I don't have a sense of how big it would be if all
On 8/10/12 1:31 PM, "Carol Frampton" wrote:
>
> don't think it works on a mac but SmartGit might be a possibility
>
SmartGit looks like SmartSVN. I think we are using it for commercial
purposes and will have to buy licenses.
Anyway, I still am unable to find a way to clone from the Apache
On 8/10/12 4 :19PM, "Dasa Paddock" wrote:
>I've never used it but TortoiseGit is a port of TortoiseSVN that looks
>good for people who liked that:
>http://code.google.com/p/tortoisegit/
don't think it works on a mac but SmartGit might be a possibility
Carol
I've never used it but TortoiseGit is a port of TortoiseSVN that looks good for
people who liked that:
http://code.google.com/p/tortoisegit/
On Aug 10, 2012, at 12:54 PM, Om wrote:
>>
>> I don't use FB other than for editing. I use SmartSVN for SVN. I was
>>
> hoping GitHub for Mac would be
>
> I don't use FB other than for editing. I use SmartSVN for SVN. I was
>
hoping GitHub for Mac would be the equivalent, but not so sure yet.
>
> The CLI seemed much more like SVN and worked for cloning from github, but I
> am getting a timeout trying to clone from git.apache.org. Is it suppos
On 8/10/12 2 :55PM, "Omar Gonzalez" wrote:
>>
>> I'm guessing we are one of the larger
>> projects at Apache in terms of code size
>
>
>This is precisely why I think we should strongly consider moving to Git.
>
>I understand the apprehension some may have with learn "Yet Another SCM
>Control",
Would we try to migrate the revision history from Subversion to Git?
- Gordon
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Friday, August 10, 2012 12:32 PM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
On 8/10/12 12:22 PM
take to move to Git?
On Fri, Aug 10, 2012 at 12:12 PM, Gordon Smith wrote:
> I only know two... I've used Perforce and Subversion for 20 years. For
> me, the most important thing is ease of use, such as what visual tools
> it has and how it integrates with IDEs like Eclipse.
Here
On 8/10/12 12:22 PM, "labri...@digitalprimates.net"
wrote:
>
>> I am greatly concerned about disk space utilization if you have a snapshot of
>> everything including changes. Has anyone synced up with Apache Flex Git
>> since we stuffed it with Mustella tests? Will each >branch/fork/clone w
> Alex:
>
>> I've spent the morning trying to use Git. I gave up and am now reading the
>> doc, because it is so different from SVN. I tried a GUI (GitHub for Mac)
>> but it seems tied to GitHub. I don't know how to redirect it to look at
>> git.apache.org. The GUI loves to show me commit rec
e-
> From: Omar Gonzalez [mailto:omarg.develo...@gmail.com]
> Sent: Friday, August 10, 2012 11:55 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: What would it take to move to Git?
>
> >
> > I'm guessing we are one of the larger projects at Apache in terms of
> > cod
>I only know two... I've used Perforce and Subversion for 20 years. For me, the
>most important thing is ease of use, such as what visual tools it has and how
>it integrates with IDEs like Eclipse. With Git, can you do >an Eclipse
>refactoring without worrying about which files you need to check
>I am greatly concerned about disk space utilization if you have a snapshot of
>everything including changes. Has anyone synced up with Apache Flex Git since
>we stuffed it with Mustella tests? Will each >branch/fork/clone we make
>actually replicate all of that data?
Alex,
Due to the way g
--Original Message-
From: Omar Gonzalez [mailto:omarg.develo...@gmail.com]
Sent: Friday, August 10, 2012 11:55 AM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
>
> I'm guessing we are one of the larger projects at Apache in terms of
> code size
On Fri, Aug 10, 2012 at 11:55 AM, Omar Gonzalez
wrote:
> >
> > I'm guessing we are one of the larger
> > projects at Apache in terms of code size
>
>
> This is precisely why I think we should strongly consider moving to Git.
>
> I understand the apprehension some may have with learn "Yet Another
one we can figure out when to make
> the actual move and set a date and make a transition. Work on SVN can
> continue the whole time.
>
There's no guarantee the project will decide to move to Git, but if you can
show us how to get there that will probably help.
I've spent the morn
>
> I'm guessing we are one of the larger
> projects at Apache in terms of code size
This is precisely why I think we should strongly consider moving to Git.
I understand the apprehension some may have with learn "Yet Another SCM
Control", but really? How many other SCM systems have you used be
August 10, 2012 7:31 AM
> To: flex-dev@incubator.apache.org
> Subject: Re: What would it take to move to Git?
>
>
>
> On 8/10/12 5 :00AM, "Carlos Rovira" wrote:
>
>> We must take into account that low activity was due to donation and
>> create a first incubation
development branches?
- Gordon
-Original Message-
From: Carol Frampton [mailto:cfram...@adobe.com]
Sent: Friday, August 10, 2012 7:31 AM
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
On 8/10/12 5 :00AM, "Carlos Rovira" wrote:
>We must take
ilto:cfram...@adobe.com]
Sent: 10 August 2012 15:31
To: flex-dev@incubator.apache.org
Subject: Re: What would it take to move to Git?
Personally I'd like to come up with a relatively simple scheme for
branching using SVN and then get to work, especially since Apache infra
still considers Git experimental
On 8/10/12 5 :00AM, "Carlos Rovira" wrote:
>We must take into account that low activity was due to donation and create
>a first incubation SDK. In the next months more people should come to the
>project as it helps to develop some patch, bug or modification.
>
>The infrastructure should support
We must take into account that low activity was due to donation and create
a first incubation SDK. In the next months more people should come to the
project as it helps to develop some patch, bug or modification.
The infrastructure should support huge changes and must be set up before
those change
On Fri, Aug 10, 2012 at 1:44 AM, Bertrand Delacretaz wrote:
> On Fri, Aug 10, 2012 at 10:30 AM, Omar Gonzalez
> wrote:
> > ...The issue, as I see it, is that the best branching model to follow
> works
> > best in Git because of the much improved manner in which it handles
> > branching, merging,
On Fri, Aug 10, 2012 at 10:30 AM, Omar Gonzalez
wrote:
> ...The issue, as I see it, is that the best branching model to follow works
> best in Git because of the much improved manner in which it handles
> branching, merging, and additional features that SVN does not have such as
> Rebasing and eas
>
>
>
> Let me add one BIG WARNING as a mentor: branches might be much easier
> to manage with Git, but if a move to Git is a way to avoid agreeing on
> how branches are managed, that won't help IMO. I would recommend
> sorting that problem (which is a community problem,
Here's an blog post that describes how you can pull changes from anyone's
Git fork:
http://bradlyfeeley.com/2008/09/03/update-a-github-fork-from-the-original-repo/
-omar
1 - 100 of 116 matches
Mail list logo
