You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Kessler CTR Mark J <ma...@usmc.mil> on 2014/09/02 14:31:04 UTC
RE: How to manage flex-utilities git repo
+1
I like the idea. I can see Justin's concerns too. Is there a way to have multiple github repos one with each of the dev-subprojects ?
-Mark
-----Original Message-----
From: Christofer Dutz [mailto:christofer.dutz@c-ware.de]
Sent: Saturday, August 30, 2014 11:14 AM
To: 'dev@flex.apache.org'
Subject: How to manage flex-utilities git repo
Hi,
while working on Squiggly, FlexPMD and the Mavenizer I too realized that the way we are currently doing things here is far from ideal as merging stuff back to master is allmost impossible.
How about not having a "develop" branch, but one for each sub-project. So when I start working on the mavenizer, I checkout "develop-mavenizer" and branch from that. As soon as my feature is finished, I merge my stuff from my feature branch back to "develop-mavenizer" now ... when a new version of the mavenizer is done, all I have to do, is merge everything oft he "develop-mavenizer" branch to master and don't have to think about what's in and what's not.
Just a thought ...
Chris
AW: How to manage flex-utilities git repo
Posted by Christofer Dutz <ch...@c-ware.de>.
Have to admit that I don't know how to extract parts of a repo.
But a quick google got me to this:
http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository
Which references this one:
http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository/17864475#17864475
(I particular like the headline "The Easy Way") ;-)
Chris
________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 3. September 2014 17:04
An: dev@flex.apache.org; Kessler CTR Mark J
Betreff: RE: How to manage flex-utilities git repo
Do any git experts know what our options are?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Kessler CTR Mark J <ma...@usmc.mil> wrote:
That could work. So when we push a branch to the new repo, are we going to delete the files we don't need out of there? This will also leave the history of the other files as well I presume.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, September 02, 2014 3:17 PM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
Infra responded rather quickly to the flex-radii8 request. It would be
already created but I didn't tell them if it was supposed to be a bare
repo or an import of another repo.
So, I think we should break up flex-utilities. At the top-level is:
ApacheFXG
FlexPMD
Squiggly
Common
installerLocaleEditor
CodeCoverage
MD5Checker
TourDeFlex
Installer
maven-flex-plugin
FXGTools
MobileTrader
ant_on_air
installerBadge
Mavenizer
I would argue that we should leave the following in flex-utilities. I
guess it sort of means that flex-utilities is for code that we don't have
release plans for, but help us do other things like modify FXG files, or
check MD5s. If we end up wanting to release something in flex-utilities,
hopefully we can later move it to its own repo without losing history.
ApacheFXG
FXGTools
MD5Checker
MobileTrader
CodeCoverage
Then we should create more repos as follows:
flex-installer.git:
ant_on_air
Common
Installer
installerBadge
installerLocaleEditor
flex-maven.git:
Maven-flex-plugin
Mavenizer
flex-squiggly.git
Squiggly
flex-pmd.git
FlexPMD
flex-tdf.git
TourDeFlex
Thoughts?
-Alex
On 9/2/14 9:26 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>Well that is probably the ideal method to have each repo for each
>utility. I believe you can push a branch to a new repository. We could
>test this out on a github throw away repo. But if not, I still like the
>branch separation as a second best.
>
>
>-Mark
>
>-----Original Message-----
>From: Alex Harui [mailto:aharui@adobe.com]
>Sent: Tuesday, September 02, 2014 11:57 AM
>To: dev@flex.apache.org
>Subject: Re: How to manage flex-utilities git repo
>
>
>
>On 9/2/14 5:31 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>
>>+1
>>
>>I like the idea. I can see Justin's concerns too. Is there a way to
>>have multiple github repos one with each of the dev-subprojects ?
>I've asked for a new repo for radii8. We'll see how quick it is to get
>one. If you look at the total set of ASF git repos it is clear that a few
>other projects like Cordova and CouchDB have many more repos than we do,
>so maybe the best answer is to split out flex-utilities into separate
>repos. Not sure how to move stuff to another repo with history.
>
>-Alex
>
RE: How to manage flex-utilities git repo
Posted by Alex Harui <ah...@adobe.com>.
Do any git experts know what our options are?
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Kessler CTR Mark J <ma...@usmc.mil> wrote:
That could work. So when we push a branch to the new repo, are we going to delete the files we don't need out of there? This will also leave the history of the other files as well I presume.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, September 02, 2014 3:17 PM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
Infra responded rather quickly to the flex-radii8 request. It would be
already created but I didn't tell them if it was supposed to be a bare
repo or an import of another repo.
So, I think we should break up flex-utilities. At the top-level is:
ApacheFXG
FlexPMD
Squiggly
Common
installerLocaleEditor
CodeCoverage
MD5Checker
TourDeFlex
Installer
maven-flex-plugin
FXGTools
MobileTrader
ant_on_air
installerBadge
Mavenizer
I would argue that we should leave the following in flex-utilities. I
guess it sort of means that flex-utilities is for code that we don't have
release plans for, but help us do other things like modify FXG files, or
check MD5s. If we end up wanting to release something in flex-utilities,
hopefully we can later move it to its own repo without losing history.
ApacheFXG
FXGTools
MD5Checker
MobileTrader
CodeCoverage
Then we should create more repos as follows:
flex-installer.git:
ant_on_air
Common
Installer
installerBadge
installerLocaleEditor
flex-maven.git:
Maven-flex-plugin
Mavenizer
flex-squiggly.git
Squiggly
flex-pmd.git
FlexPMD
flex-tdf.git
TourDeFlex
Thoughts?
-Alex
On 9/2/14 9:26 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>Well that is probably the ideal method to have each repo for each
>utility. I believe you can push a branch to a new repository. We could
>test this out on a github throw away repo. But if not, I still like the
>branch separation as a second best.
>
>
>-Mark
>
>-----Original Message-----
>From: Alex Harui [mailto:aharui@adobe.com]
>Sent: Tuesday, September 02, 2014 11:57 AM
>To: dev@flex.apache.org
>Subject: Re: How to manage flex-utilities git repo
>
>
>
>On 9/2/14 5:31 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>
>>+1
>>
>>I like the idea. I can see Justin's concerns too. Is there a way to
>>have multiple github repos one with each of the dev-subprojects ?
>I've asked for a new repo for radii8. We'll see how quick it is to get
>one. If you look at the total set of ASF git repos it is clear that a few
>other projects like Cordova and CouchDB have many more repos than we do,
>so maybe the best answer is to split out flex-utilities into separate
>repos. Not sure how to move stuff to another repo with history.
>
>-Alex
>
RE: How to manage flex-utilities git repo
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
That could work. So when we push a branch to the new repo, are we going to delete the files we don't need out of there? This will also leave the history of the other files as well I presume.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, September 02, 2014 3:17 PM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
Infra responded rather quickly to the flex-radii8 request. It would be
already created but I didn't tell them if it was supposed to be a bare
repo or an import of another repo.
So, I think we should break up flex-utilities. At the top-level is:
ApacheFXG
FlexPMD
Squiggly
Common
installerLocaleEditor
CodeCoverage
MD5Checker
TourDeFlex
Installer
maven-flex-plugin
FXGTools
MobileTrader
ant_on_air
installerBadge
Mavenizer
I would argue that we should leave the following in flex-utilities. I
guess it sort of means that flex-utilities is for code that we don't have
release plans for, but help us do other things like modify FXG files, or
check MD5s. If we end up wanting to release something in flex-utilities,
hopefully we can later move it to its own repo without losing history.
ApacheFXG
FXGTools
MD5Checker
MobileTrader
CodeCoverage
Then we should create more repos as follows:
flex-installer.git:
ant_on_air
Common
Installer
installerBadge
installerLocaleEditor
flex-maven.git:
Maven-flex-plugin
Mavenizer
flex-squiggly.git
Squiggly
flex-pmd.git
FlexPMD
flex-tdf.git
TourDeFlex
Thoughts?
-Alex
On 9/2/14 9:26 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>Well that is probably the ideal method to have each repo for each
>utility. I believe you can push a branch to a new repository. We could
>test this out on a github throw away repo. But if not, I still like the
>branch separation as a second best.
>
>
>-Mark
>
>-----Original Message-----
>From: Alex Harui [mailto:aharui@adobe.com]
>Sent: Tuesday, September 02, 2014 11:57 AM
>To: dev@flex.apache.org
>Subject: Re: How to manage flex-utilities git repo
>
>
>
>On 9/2/14 5:31 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>
>>+1
>>
>>I like the idea. I can see Justin's concerns too. Is there a way to
>>have multiple github repos one with each of the dev-subprojects ?
>I've asked for a new repo for radii8. We'll see how quick it is to get
>one. If you look at the total set of ASF git repos it is clear that a few
>other projects like Cordova and CouchDB have many more repos than we do,
>so maybe the best answer is to split out flex-utilities into separate
>repos. Not sure how to move stuff to another repo with history.
>
>-Alex
>
Re: How to manage flex-utilities git repo
Posted by Alex Harui <ah...@adobe.com>.
Infra responded rather quickly to the flex-radii8 request. It would be
already created but I didn't tell them if it was supposed to be a bare
repo or an import of another repo.
So, I think we should break up flex-utilities. At the top-level is:
ApacheFXG
FlexPMD
Squiggly
Common
installerLocaleEditor
CodeCoverage
MD5Checker
TourDeFlex
Installer
maven-flex-plugin
FXGTools
MobileTrader
ant_on_air
installerBadge
Mavenizer
I would argue that we should leave the following in flex-utilities. I
guess it sort of means that flex-utilities is for code that we don't have
release plans for, but help us do other things like modify FXG files, or
check MD5s. If we end up wanting to release something in flex-utilities,
hopefully we can later move it to its own repo without losing history.
ApacheFXG
FXGTools
MD5Checker
MobileTrader
CodeCoverage
Then we should create more repos as follows:
flex-installer.git:
ant_on_air
Common
Installer
installerBadge
installerLocaleEditor
flex-maven.git:
Maven-flex-plugin
Mavenizer
flex-squiggly.git
Squiggly
flex-pmd.git
FlexPMD
flex-tdf.git
TourDeFlex
Thoughts?
-Alex
On 9/2/14 9:26 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>Well that is probably the ideal method to have each repo for each
>utility. I believe you can push a branch to a new repository. We could
>test this out on a github throw away repo. But if not, I still like the
>branch separation as a second best.
>
>
>-Mark
>
>-----Original Message-----
>From: Alex Harui [mailto:aharui@adobe.com]
>Sent: Tuesday, September 02, 2014 11:57 AM
>To: dev@flex.apache.org
>Subject: Re: How to manage flex-utilities git repo
>
>
>
>On 9/2/14 5:31 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>
>>+1
>>
>>I like the idea. I can see Justin's concerns too. Is there a way to
>>have multiple github repos one with each of the dev-subprojects ?
>I've asked for a new repo for radii8. We'll see how quick it is to get
>one. If you look at the total set of ASF git repos it is clear that a few
>other projects like Cordova and CouchDB have many more repos than we do,
>so maybe the best answer is to split out flex-utilities into separate
>repos. Not sure how to move stuff to another repo with history.
>
>-Alex
>
RE: How to manage flex-utilities git repo
Posted by Kessler CTR Mark J <ma...@usmc.mil>.
Well that is probably the ideal method to have each repo for each utility. I believe you can push a branch to a new repository. We could test this out on a github throw away repo. But if not, I still like the branch separation as a second best.
-Mark
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, September 02, 2014 11:57 AM
To: dev@flex.apache.org
Subject: Re: How to manage flex-utilities git repo
On 9/2/14 5:31 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>+1
>
>I like the idea. I can see Justin's concerns too. Is there a way to
>have multiple github repos one with each of the dev-subprojects ?
I've asked for a new repo for radii8. We'll see how quick it is to get
one. If you look at the total set of ASF git repos it is clear that a few
other projects like Cordova and CouchDB have many more repos than we do,
so maybe the best answer is to split out flex-utilities into separate
repos. Not sure how to move stuff to another repo with history.
-Alex
Re: How to manage flex-utilities git repo
Posted by Alex Harui <ah...@adobe.com>.
On 9/2/14 5:31 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:
>+1
>
>I like the idea. I can see Justin's concerns too. Is there a way to
>have multiple github repos one with each of the dev-subprojects ?
I've asked for a new repo for radii8. We'll see how quick it is to get
one. If you look at the total set of ASF git repos it is clear that a few
other projects like Cordova and CouchDB have many more repos than we do,
so maybe the best answer is to split out flex-utilities into separate
repos. Not sure how to move stuff to another repo with history.
-Alex