On Sep 05, 2014, at 07:03 PM, Niko Tyni wrote:
>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
This works brilliantly, thanks!
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 l
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
On Fri, Sep 05, 2014 at 10:26:52AM -0400, Barry Warsaw wrote:
> Package: git-dpm
> Version: 0.8.5-1
> Severity: wishlist
> Also, it would be nice if we could control the rest of the name of the
> patch file.
Are you aware of the Patch-Name header? See #602272.
--
Niko Tyni nt...@debian.org
-
Package: git-dpm
Version: 0.8.5-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
Currently, update-patches emits d/patches files that start with a 4
digit number and a dash-separated list of words which are taken from
the first line of the Subject: header. I
5 matches
Mail list logo
