If you want a GUI for git svn commands the Tower app has support. Also, git
svn commands should come with a standard Git installation, at least I
didn't have to install that separately.
-omar
> I would look at the git svn commands and manage my work from there if I
> wasn't a committer. I believe it'll even let you create patches from your
> Git branch for SVN.
Yep that works but it don't preserve checkins or commits (to git). So when your
code gets checked in to SVN it will a miss a
On Wednesday, January 25, 2012, Justin Mclean
wrote:
>
>> It doesn't have to go under the committer's name.
>>
>> I could easily create a folder named 'McClean' and your code could go in
>> there, while I still have my own folder.
>
> That's good to know.
>
> Any idea how version control comments
I think I'll just stick with "org.apache.flex...", we'll have to support
legacy with Flex SDK so it doesn't make sense to change the
"spark.components..." etc namespaces.
Plus like someone said, its the whiteboard area.
-omar
On 17/01/2012 09:34, Omar Gonzalez wrote:
Before I started on the StringValidator I committed to my whiteboard I sat
and stared at the screen for a few minutes trying to decide which namespace
to use.
Ultimately I went with "org.apache.flex.validators" because I did not want
to confuse people by
I really think it doesn't matter at all. The code is not released and will be
moved to a more appropriate place before it gets released. At that time it will
probably be more obvious what the namespace should be.
Sent from my mobile device.
On Jan 16, 2012, at 6:34 PM, Omar Gonzalez wrote:
>
> From: Bertrand Delacretaz [mailto:bdelacre...@apache.org]
> Sent: 10 January 2012 11:03
>> ...So basically, your saying there really shouldn't be any traces of
>> copyright or author in a source file correct? Just the Apache 2 license
>> header
> In general, yes.
That sounds like a very
On Tue, Jan 10, 2012 at 11:15 AM, Michael Schmalle
wrote:
> ...So basically, your saying there really shouldn't be any traces of copyright
> or author in a source file correct? Just the Apache 2 license header
In general, yes.
-Bertrand
On Tue, Jan 10, 2012 at 11:10 AM, Peter Elst wrote:
>> In general I'd say everyone's welcome to touch any code as long as
>> they know what they are doing - and that might include asking
>> whoever's currently working on the module in question if that's ok.
>>
>
> Maybe I'm overthinking this, but
Quoting Bertrand Delacretaz :
On Mon, Jan 9, 2012 at 11:48 PM, Peter Elst wrote:
...so in general lets say somebody wants to work on
something in the whiteboard, would you create your own copy of it or put it
in the original folder?...
In general I'd say everyone's welcome to touch any code
Quoting Bertrand Delacretaz :
On Mon, Jan 9, 2012 at 11:55 PM, Jonathan Campos
wrote:
...I wasn't worried about ownership. I guess that is what header
files are for:
author: person A
contributors: person B, C, and D
If you mean adding that in source file headers, that's frowned upon
at A
> In general I'd say everyone's welcome to touch any code as long as
> they know what they are doing - and that might include asking
> whoever's currently working on the module in question if that's ok.
>
Maybe I'm overthinking this, but how would the original committer need to
be contacted? Does
On Mon, Jan 9, 2012 at 11:48 PM, Peter Elst wrote:
> ...so in general lets say somebody wants to work on
> something in the whiteboard, would you create your own copy of it or put it
> in the original folder?...
In general I'd say everyone's welcome to touch any code as long as
they know what the
On Mon, Jan 9, 2012 at 11:55 PM, Jonathan Campos wrote:
> ...I wasn't worried about ownership. I guess that is what header
> files are for:
>
> author: person A
> contributors: person B, C, and D
If you mean adding that in source file headers, that's frowned upon at Apache.
The problem is that d
+1
Original Message
> From: "Dirk Eismann"
> Sent: terça-feira, 10 de Janeiro de 2012 7:44
> To: flex-dev@incubator.apache.org
> Subject: Re: whiteboard
>
> README files are also handy when it comes to describing how to set up the
> project, build
README files are also handy when it comes to describing how to set up the
project, build it, list required dependencies etc.
Dirk.
I don't mind either approach (named folders or name in folder name) but I
think we can all agree that we should all add README files to our
whiteboard experiments just for courtesy, you never know how you might
inspire someone to make a new feature or improvement.
-omar
On Mon, Jan 9, 2012 at 8:21 PM, Doug Arthur wrote:
> Why not just require a README.txt in each whiteboard folder, and the
> responsible developer can place valuable notes on the work being done,
> including if they want everyone else hands off.
>
Like the README.txt. Great addition.
I still wou
On Jan 9, 2012 5:01 PM, "Rui Silva" wrote:
> Yet another approach that is kind of middle ground would be to not
separate
> by username, but to include the author's username in the branch name
> alongside with the feature of the branch (I think it was Omar who
suggested
> this).
Why not just requi
ng worked on).
Best,
Rui
Original Message
> From: "Peter Elst"
> Sent: segunda-feira, 9 de Janeiro de 2012 22:46
> To: flex-dev@incubator.apache.org
> Subject: Re: whiteboard
>
> > I don't think I have to say that I would never go into something and
>
On Mon, Jan 9, 2012 at 4:48 PM, Peter Elst wrote:
> I'm just asking because with the username in the folder, the situation
> could arise that the code was originally put in the whiteboard by own
> committer but 99% of the code got contributed by somebody else.
>
In my case I wasn't worried about
Quoting Peter Elst :
I don't think I have to say that I would never go into something and
delete stuff without talking to the contributor.
my mistake, sorry Mike - so in general lets say somebody wants to work on
something in the whiteboard, would you create your own copy of it or put it
in
> I don't think I have to say that I would never go into something and
> delete stuff without talking to the contributor.
>
my mistake, sorry Mike - so in general lets say somebody wants to work on
something in the whiteboard, would you create your own copy of it or put it
in the original folder?
Quoting Peter Elst :
Sounds like things need to be talked about here, I would suggest you list
out some other things if you have them.
Also agree with Jonathan on getting some structure in the whiteboard and
using username folders.
It would be good to know how we define the whiteboard stuff
> Sounds like things need to be talked about here, I would suggest you list
> out some other things if you have them.
>
Also agree with Jonathan on getting some structure in the whiteboard and
using username folders.
It would be good to know how we define the whiteboard stuff, I assumed it
was p
Quoting Jonathan Campos :
On Mon, Jan 9, 2012 at 4:22 PM, Michael Schmalle
wrote:
Sounds like things need to be talked about here, I would suggest you list
out some other things if you have them.
I can't remember the exact response but I want to say it was shown in
previous examples to be
On Mon, Jan 9, 2012 at 4:22 PM, Michael Schmalle wrote:
> Sounds like things need to be talked about here, I would suggest you list
> out some other things if you have them.
I can't remember the exact response but I want to say it was shown in
previous examples to be using the username.
I wasn'
On Jan 9, 2012, at 3:22 PM, Michael Schmalle wrote:
> Quoting Jonathan Campos :
>
>> I'm watching the whiteboard and it would be great if people could keep the
>> whiteboard separated by originator's name.
>>
>> whiteboard
>> > jonbcampos
>> > content
>> > etc
I would agree with Jon on this.
Quoting Jonathan Campos :
I'm watching the whiteboard and it would be great if people could keep the
whiteboard separated by originator's name.
whiteboard
> jonbcampos
> content
> etc
This way we don't conflict with:
whiteboard
> di
> di-idea2
> different-di-idea
> tabnavigator
> tab
29 matches
Mail list logo
