[INFRA][VFS][DISCUSS] Git pull notification mails to dev@

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[INFRA][VFS][DISCUSS] Git pull notification mails to dev@

Bernd Eckenfels
Hello,

while we are at the topic of helping future commiters, including Git and  
workflow I would like to ask/remind about this JIRA:

https://issues.apache.org/jira/browse/INFRA-6764

It is about enabling pull notification mails for [VFS] and havent seen  
much activity yet. (Maybe I should not open bugs with minor priority? :)

BTW: I think the patch/diff generated by Github are not much different  
 from Jira uploaded diffs. They are just more consitent and come with a  
nice web view. IMHO they should fit pretty well into any developers SVN  
workflow (maybe the prefix length issue needs to be figured out once).

BTW2: just to voice a different oppinion, contributing to a CVS project is  
for me easier than contributing to a SVN project where you always have to  
wonder about trunks, branches and parent. It took me quite some time to  
check out a working VFS parent with SVN. With Git it was no problem (and  
with CVS I suppose it would be similiar easy). Of course this could be a  
tooling problem, but I am stuck with Eclipse :)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [INFRA][VFS][DISCUSS] Git pull notification mails to dev@

garydgregory
Why not simply switch to Git?

Gary

On Tue, Oct 8, 2013 at 5:57 PM, Bernd Eckenfels <[hidden email]> wrote:

> Hello,
>
> while we are at the topic of helping future commiters, including Git and
> workflow I would like to ask/remind about this JIRA:
>
> https://issues.apache.org/jira/browse/INFRA-6764
>
> It is about enabling pull notification mails for [VFS] and havent seen much
> activity yet. (Maybe I should not open bugs with minor priority? :)
>
> BTW: I think the patch/diff generated by Github are not much different from
> Jira uploaded diffs. They are just more consitent and come with a nice web
> view. IMHO they should fit pretty well into any developers SVN workflow
> (maybe the prefix length issue needs to be figured out once).
>
> BTW2: just to voice a different oppinion, contributing to a CVS project is
> for me easier than contributing to a SVN project where you always have to
> wonder about trunks, branches and parent. It took me quite some time to
> check out a working VFS parent with SVN. With Git it was no problem (and
> with CVS I suppose it would be similiar easy). Of course this could be a
> tooling problem, but I am stuck with Eclipse :)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>



--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [INFRA][VFS][DISCUSS] Git pull notification mails to dev@

James Carman
+1!!!

On Tue, Oct 8, 2013 at 6:07 PM, Gary Gregory <[hidden email]> wrote:

> Why not simply switch to Git?
>
> Gary
>
> On Tue, Oct 8, 2013 at 5:57 PM, Bernd Eckenfels <[hidden email]> wrote:
>> Hello,
>>
>> while we are at the topic of helping future commiters, including Git and
>> workflow I would like to ask/remind about this JIRA:
>>
>> https://issues.apache.org/jira/browse/INFRA-6764
>>
>> It is about enabling pull notification mails for [VFS] and havent seen much
>> activity yet. (Maybe I should not open bugs with minor priority? :)
>>
>> BTW: I think the patch/diff generated by Github are not much different from
>> Jira uploaded diffs. They are just more consitent and come with a nice web
>> view. IMHO they should fit pretty well into any developers SVN workflow
>> (maybe the prefix length issue needs to be figured out once).
>>
>> BTW2: just to voice a different oppinion, contributing to a CVS project is
>> for me easier than contributing to a SVN project where you always have to
>> wonder about trunks, branches and parent. It took me quite some time to
>> check out a working VFS parent with SVN. With Git it was no problem (and
>> with CVS I suppose it would be similiar easy). Of course this could be a
>> tooling problem, but I am stuck with Eclipse :)
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> E-Mail: [hidden email] | [hidden email]
> Java Persistence with Hibernate, Second Edition
> JUnit in Action, Second Edition
> Spring Batch in Action
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]