Re: Git for source control

[Daniel Brownridge]

Don't like!


On 21/03/18 14:04, Daniel Brownridge wrote:
> like HTML email either

Re: Git for source control

[Daniel Brownridge]

@Gary, I understand, like HTML email either. Octocat was just there to
make you smile.


On 21/03/18 12:44, Gary Martin wrote:
> On Mon, 19 Mar 2018, at 3:03 PM, Daniel Brownridge wrote:
>> I like git!
> Just remembered how much I dislike html for emails. That comment was hidden 
> from view for me and I didn't spot the alt text.
>
> /me searches mail client options.
>
>>  
>> On 19/03/18 14:55, Gary Martin wrote:
>>> Hi everyone,
> As pointed out in another thread, I have not looked for any consensus on use 
> of git for issue tracking for work on a trac-less bloodhound. Part of the 
> reason would be my imperfect memory of discussions around making more use of 
> git and similar.
>
> There are a number of options for how to continue. It could be argued that 
> there is no strict need to move away from subversion as we have git mirroring 
> already. Indeed, this discussion around git does not impact on the ability to 
> experiment with new directions in the short term.
>
> What I feel we definitely need is to start ensuring that we support git as 
> part of our development workflow. I expect that to be achievable regardless.
>
> I hope none of the above reveals any bias towards one side or another as I do 
> not wish to prejudice this discussion.
>
> Please let us know your thoughts.
>
> Cheers,
> Gary
> --
> Cheers,
>     Gary

Re: Git for source control

[Gary Martin]

On Wed, 21 Mar 2018, at 12:44 PM, Gary Martin wrote:
> On Mon, 19 Mar 2018, at 3:03 PM, Daniel Brownridge wrote:
> > I like git!
> 
> Just remembered how much I dislike html for emails. That comment was 
> hidden from view for me and I didn't spot the alt text.
> 
> /me searches mail client options.
> 

and my apologies for that last message making it look like I was saying more 
than the above :(

-- 
Cheers,
Gary

Re: Git for source control

[Gary Martin]

On Mon, 19 Mar 2018, at 3:03 PM, Daniel Brownridge wrote:
> I like git!

Just remembered how much I dislike html for emails. That comment was hidden 
from view for me and I didn't spot the alt text.

/me searches mail client options.

>  
> On 19/03/18 14:55, Gary Martin wrote:
>> Hi everyone,

As pointed out in another thread, I have not looked for any consensus on use of 
git for issue tracking for work on a trac-less bloodhound. Part of the reason 
would be my imperfect memory of discussions around making more use of git and 
similar.

There are a number of options for how to continue. It could be argued that 
there is no strict need to move away from subversion as we have git mirroring 
already. Indeed, this discussion around git does not impact on the ability to 
experiment with new directions in the short term.

What I feel we definitely need is to start ensuring that we support git as part 
of our development workflow. I expect that to be achievable regardless.

I hope none of the above reveals any bias towards one side or another as I do 
not wish to prejudice this discussion.

Please let us know your thoughts.

Cheers,
Gary
>> 
> 

--
Cheers,
    Gary

Re: Git for source control

[Allan Swanepoel]

Another +1 for git

On Mon, 19 Mar 2018, 18:33 John Chambers,  wrote:

> It's a +1 for git from me.
>
> Cheers
>
> John.
>
> On 19 March 2018 at 15:10, Dammina Sahabandu 
> wrote:
>
> > Hi All/Gary,
> >
> > Git overweighs svn in many ways. So +1 for Git.
> >
> > Also, apologies about the less involvement in the other thread. I still
> > couldn't catch a free moment to go through it. But its great to see ideas
> > being shared. Lets keep it up.
> >
> > Thanks,
> > Dammina
> >
> > On Mon, Mar 19, 2018 at 11:03 PM, Daniel Brownridge <
> > daniel.brownri...@gmail.com> wrote:
> >
> >> [image: I like git!]
> >>
> >> On 19/03/18 14:55, Gary Martin wrote:
> >>
> >> Hi everyone,
> >>
> >> As pointed out in another thread, I have not looked for any consensus
> on use of git for issue tracking for work on a trac-less bloodhound. Part
> of the reason would be my imperfect memory of discussions around making
> more use of git and similar.
> >>
> >> There are a number of options for how to continue. It could be argued
> that there is no strict need to move away from subversion as we have git
> mirroring already. Indeed, this discussion around git does not impact on
> the ability to experiment with new directions in the short term.
> >>
> >> What I feel we definitely need is to start ensuring that we support git
> as part of our development workflow. I expect that to be achievable
> regardless.
> >>
> >> I hope none of the above reveals any bias towards one side or another
> as I do not wish to prejudice this discussion.
> >>
> >> Please let us know your thoughts.
> >>
> >> Cheers,
> >> Gary
> >>
> >>
> >>
> >
> >
> > --
> > Dammina Sahabandu
> > PMC & Committer, Apache Software Foundation
> > AMIE (SL)
> > Bsc Eng Hons (Moratuwa)
> > +65 881 129 81
> >
>

Re: Git for source control

[John Chambers]

It's a +1 for git from me.

Cheers

John.

On 19 March 2018 at 15:10, Dammina Sahabandu  wrote:

> Hi All/Gary,
>
> Git overweighs svn in many ways. So +1 for Git.
>
> Also, apologies about the less involvement in the other thread. I still
> couldn't catch a free moment to go through it. But its great to see ideas
> being shared. Lets keep it up.
>
> Thanks,
> Dammina
>
> On Mon, Mar 19, 2018 at 11:03 PM, Daniel Brownridge <
> daniel.brownri...@gmail.com> wrote:
>
>> [image: I like git!]
>>
>> On 19/03/18 14:55, Gary Martin wrote:
>>
>> Hi everyone,
>>
>> As pointed out in another thread, I have not looked for any consensus on use 
>> of git for issue tracking for work on a trac-less bloodhound. Part of the 
>> reason would be my imperfect memory of discussions around making more use of 
>> git and similar.
>>
>> There are a number of options for how to continue. It could be argued that 
>> there is no strict need to move away from subversion as we have git 
>> mirroring already. Indeed, this discussion around git does not impact on the 
>> ability to experiment with new directions in the short term.
>>
>> What I feel we definitely need is to start ensuring that we support git as 
>> part of our development workflow. I expect that to be achievable regardless.
>>
>> I hope none of the above reveals any bias towards one side or another as I 
>> do not wish to prejudice this discussion.
>>
>> Please let us know your thoughts.
>>
>> Cheers,
>> Gary
>>
>>
>>
>
>
> --
> Dammina Sahabandu
> PMC & Committer, Apache Software Foundation
> AMIE (SL)
> Bsc Eng Hons (Moratuwa)
> +65 881 129 81
>

Re: Git for source control

[Dammina Sahabandu]

Hi All/Gary,

Git overweighs svn in many ways. So +1 for Git.

Also, apologies about the less involvement in the other thread. I still
couldn't catch a free moment to go through it. But its great to see ideas
being shared. Lets keep it up.

Thanks,
Dammina

On Mon, Mar 19, 2018 at 11:03 PM, Daniel Brownridge <
daniel.brownri...@gmail.com> wrote:

> [image: I like git!]
>
> On 19/03/18 14:55, Gary Martin wrote:
>
> Hi everyone,
>
> As pointed out in another thread, I have not looked for any consensus on use 
> of git for issue tracking for work on a trac-less bloodhound. Part of the 
> reason would be my imperfect memory of discussions around making more use of 
> git and similar.
>
> There are a number of options for how to continue. It could be argued that 
> there is no strict need to move away from subversion as we have git mirroring 
> already. Indeed, this discussion around git does not impact on the ability to 
> experiment with new directions in the short term.
>
> What I feel we definitely need is to start ensuring that we support git as 
> part of our development workflow. I expect that to be achievable regardless.
>
> I hope none of the above reveals any bias towards one side or another as I do 
> not wish to prejudice this discussion.
>
> Please let us know your thoughts.
>
> Cheers,
> Gary
>
>
>


-- 
Dammina Sahabandu
PMC & Committer, Apache Software Foundation
AMIE (SL)
Bsc Eng Hons (Moratuwa)
+65 881 129 81

Re: Git for source control

[Daniel Brownridge]

I like git!
On 19/03/18 14:55, Gary Martin wrote:
> Hi everyone,
>
> As pointed out in another thread, I have not looked for any consensus on use 
> of git for issue tracking for work on a trac-less bloodhound. Part of the 
> reason would be my imperfect memory of discussions around making more use of 
> git and similar.
>
> There are a number of options for how to continue. It could be argued that 
> there is no strict need to move away from subversion as we have git mirroring 
> already. Indeed, this discussion around git does not impact on the ability to 
> experiment with new directions in the short term.
>
> What I feel we definitely need is to start ensuring that we support git as 
> part of our development workflow. I expect that to be achievable regardless.
>
> I hope none of the above reveals any bias towards one side or another as I do 
> not wish to prejudice this discussion.
>
> Please let us know your thoughts.
>
> Cheers,
> Gary

Git for source control

[Gary Martin]

Hi everyone,

As pointed out in another thread, I have not looked for any consensus on use of 
git for issue tracking for work on a trac-less bloodhound. Part of the reason 
would be my imperfect memory of discussions around making more use of git and 
similar.

There are a number of options for how to continue. It could be argued that 
there is no strict need to move away from subversion as we have git mirroring 
already. Indeed, this discussion around git does not impact on the ability to 
experiment with new directions in the short term.

What I feel we definitely need is to start ensuring that we support git as part 
of our development workflow. I expect that to be achievable regardless.

I hope none of the above reveals any bias towards one side or another as I do 
not wish to prejudice this discussion.

Please let us know your thoughts.

Cheers,
Gary