Re: git-cl upload and existing sf issues

On Nov 2, 2019, at 12:35, Dan Eble wrote: > >> when uploading a first patch set, git-cl asks for a sourceforge issue >> number. If a new issue is created, everything is fine but when you choose an >> existing issue, there is some 404 error and the Rietveld link is not added >> to the sf

Re: git-cl upload and existing sf issues

On Sep 30, 2019, at 16:54, Malte Meyn wrote: > > when uploading a first patch set, git-cl asks for a sourceforge issue number. > If a new issue is created, everything is fine but when you choose an existing > issue, there is some 404 error and the Rietveld link is not added to the sf >

git-cl upload and existing sf issues

Hi list, when uploading a first patch set, git-cl asks for a sourceforge issue number. If a new issue is created, everything is fine but when you choose an existing issue, there is some 404 error and the Rietveld link is not added to the sf issue—resulting in a missing Rietveld link on