On Fri, Sep 05, 2014 at 11:10:17AM -0400, Barry Warsaw wrote: > On Sep 05, 2014, at 05:36 PM, Niko Tyni wrote: > > >Are you aware of the Patch-Name header? See #602272. > > I wasn't; thanks for the pointer! However, now that I've read the > documentation and done some experimentation, it seems like it's not possible > to retrofit an existing git-dpm repo with Patch-Name. --record-patch-name is > only available on the git-dpm init and import-dsc commands afaict. > > Also, I took an existing git-dpm repo and on the master branch added a > Patch-Name header and also rewrote the Subject field. After a > checkout-patched/update-patches --redo roundtrip, these changes were not > preserved. > > So I think the current Patch-Name handling is close, but it would be really > nice if this could be preserved through an edit/cp/up cycle.
This can be done by adding the headers to the commits on the patched branch. Something like git dpm checkout-patched git commit --amend (or git rebase -i and reword all), add the header git dpm update-patches But yeah, it does seem like checkout-patched could have a --record-patch-name option so it would look at the headers in the patch files and recreate the patched branch. (Disclaimer: I'm not the maintainer, just an interested user.) -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
