On Thu, Dec 16, 2010 at 06:02:37PM +0100, IOhannes m zmoelnig wrote:
darn, i wrote a long reply to this but then we had a power failure and
the mail is gone
:-(
On Tue, Dec 14, 2010 at 05:54:36PM +0100, IOhannes m zmoelnig wrote:
shouldn't all this exclusion be documented somewhere, e.g.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
darn, i wrote a long reply to this but then we had a power failure and
the mail is gone
> On Tue, Dec 14, 2010 at 05:54:36PM +0100, IOhannes m zmoelnig wrote:
>> shouldn't all this exclusion be documented somewhere, e.g. in
>> debian/README.source
On Tue, Dec 14, 2010 at 05:54:36PM +0100, IOhannes m zmoelnig wrote:
i have a question on how the exclusion of files from the upstream
tarball can be handled and maintained.
as far as i understand, you just use
$ git-import-orig --filter="*proprietary*" /path/to/upstream_1.0.tar.gz
which will
On Tue, Dec 14, 2010 at 17:54:36 (CET), IOhannes m zmoelnig wrote:
> i have a question on how the exclusion of files from the upstream
> tarball can be handled and maintained.
>
> as far as i understand, you just use
> $ git-import-orig --filter="*proprietary*" /path/to/upstream_1.0.tar.gz
>
> whi
