Re: Git for source control

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

Re: Git for source control

@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

Re: Git for source control

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

Re: Git for source control

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

Re: Git for source control

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.

Re: Git for source control

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

Re: Git for source control

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

Re: Git for source control

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

Git for source control

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