Control: fixed -1 3.3
Control: close -1
Ian Jackson writes ("Bug#869675: extracting upstream source."):
> I hope this is of some use. I appreciate that it's a bit late to be
> replying to this now. Anyway, the above is not 100% convenient but
> ISTM that it is good enou
Control: tags -1 + moreinfo
Ian Jackson writes ("Re: extracting upstream source."):
> dgit often has "something like" the upstream source tree as a git
> tree object. dgit should provide a way for you to get at it.
Nowadays there is dgit import-dsc which goes a fair way towards this.
It is not
On Tue, Jul 25, 2017 at 03:55:08PM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: extracting upstream source."):
> > dgit often has "something like" the upstream source tree as a git tree
> > object. dgit should provide a way for you to get at it.
>
> This is now #869675.
For our Ubuntu gi
Ian Jackson writes ("Re: extracting upstream source."):
> dgit often has "something like" the upstream source tree as a git tree
> object. dgit should provide a way for you to get at it.
This is now #869675.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @f
Package: dgit
Version: 3.12
Peter Green writes ("extracting upstream source."):
> As part of my dgit based autoforwardporter I want to add a script that will
> de-fuzz patches with fuzz and remove patches that cannot be applied.
>
> To do this I need the "upstream" source tree. However the proce
5 matches
Mail list logo
