On Mon, 6 Nov 2017 08:59:41 +0100 Guido =?iso-8859-1?Q?G=FCnther?=
<[email protected]> wrote:
> Hi,
> My first reaction was to teach gbp import-orig to have a
>
>     gbp import-orig "git-ref"
>
> mode that would do the right thing but I now think having
>
>     gbp update "git-ref"
>
> that
>
>     - does the excluding and tagging if necessary
>     - merges to the debian branch
>
> is better. We need to make sure that gbp import-orig's filtering (using
> the --filter command line or filter= gbp.conf option) stays in sync with
> what we do so we don't have on tool using --filter= and the other one
> parsing debian/changelog.
>
> If somebody comes up with a better name than "update" that's all fine.
> Cheers,

I would suggest `gbp import-git`, which is consistent with `import-*`

also the "git-ref" can be parsed as an option, so we can store it in gbp.conf.

And I suggest the `--filter` option can also be remained, when
importing from upstream git.
Besides, adding an option like `--filter-with-copyright` to indicate
filtering files from "Files-Excluded" in d/copyright file.


--
Shengjing Zhu

Reply via email to