Re: patch for git-cl

2017-01-08 Thread Thomas Morley
2017-01-09 0:09 GMT+01:00 Graham Percival <gra...@percival-music.ca>: > On Sun, Jan 08, 2017 at 09:02:51PM +, Thomas Morley wrote: >> attached a little patch for git-cl to replace googlecodeissue by >> trackerissue in cl_settings.py, which will result in correct i

Re: patch for git-cl

2017-01-08 Thread Graham Percival
On Sun, Jan 08, 2017 at 09:02:51PM +, Thomas Morley wrote: > attached a little patch for git-cl to replace googlecodeissue by > trackerissue in cl_settings.py, which will result in correct info in > .git/config > > How do we handle patches to git-cl? In general, I'd recommend

Re: patch for git-cl

2017-01-08 Thread Graham Percival
On Sun, Jan 08, 2017 at 10:15:24PM +, James wrote: > On Sun, 8 Jan 2017 21:02:51 + > Thomas Morley <thomasmorle...@gmail.com> wrote: > > > attached a little patch for git-cl to replace googlecodeissue by > > trackerissue in cl_settings.py, which will result

Re: patch for git-cl

2017-01-08 Thread James
On Sun, 8 Jan 2017 21:02:51 + Thomas Morley <thomasmorle...@gmail.com> wrote: > Hi, > > attached a little patch for git-cl to replace googlecodeissue by > trackerissue in cl_settings.py, which will result in correct info in > .git/config > > How do we handle pat

patch for git-cl

2017-01-08 Thread Thomas Morley
Hi, attached a little patch for git-cl to replace googlecodeissue by trackerissue in cl_settings.py, which will result in correct info in .git/config How do we handle patches to git-cl? Cheers, Harm From b8364652a91f3e07bef7719da71f56994c69e7b3 Mon Sep 17 00:00:00 2001 From: Thomas Morley