Thanks, this did the trick.
On Fri, May 20, 2016 at 1:43 PM Mattia Rizzolo wrote:
> On Fri, May 20, 2016 at 11:10:43AM +, Nico Schlömer wrote:
> > Thanks for the hint.
> > Unfortunately, it's not working dpt picks up an older version that
> already
> > is in pristine-tar and adds another com
Hi Nico,
On 20 May 2016 at 08:10, Nico Schlömer wrote:
> Thanks for the hint.
> Unfortunately, it's not working dpt picks up an older version that already
> is in pristine-tar and adds another commit for it (bug?), but leaves out the
> version for which there is no pristine-tar.
>
> Any other sug
On Fri, May 20, 2016 at 11:10:43AM +, Nico Schlömer wrote:
> Thanks for the hint.
> Unfortunately, it's not working dpt picks up an older version that already
> is in pristine-tar and adds another commit for it (bug?), but leaves out
> the version for which there is no pristine-tar.
>
> Any ot
Thanks for the hint.
Unfortunately, it's not working dpt picks up an older version that already
is in pristine-tar and adds another commit for it (bug?), but leaves out
the version for which there is no pristine-tar.
Any other suggestions?
Cheers,
Nico
On Fri, May 20, 2016 at 12:34 PM Dominique
On Friday 20 May 2016 10:19:19 Nico Schlömer wrote:
> I've got a git-managed repo where an upstream version was included (via the
> upstream branch, merged into master), but adding a corresponding
> pristine-tar was omitted. How can I retroactively add a pristine-tar
> corresponding to an upstream
Hi everyone,
I've got a git-managed repo where an upstream version was included (via the
upstream branch, merged into master), but adding a corresponding
pristine-tar was omitted. How can I retroactively add a pristine-tar
corresponding to an upstream release?
Cheers,
Nico
6 matches
Mail list logo
