Hi Matthijs,
On Mon, Jun 28, 2010 at 08:24:30PM +0200, Matthijs Kooijman wrote:
[..snip..]
As for the general idea of this patch: I've been using it for a while now,
and
considering most of my upstream packages use a
packagename-version-source.tar.gz tarball (and considering that some of
Hi Guido,
any chance you could respond to my suggestions below? :-)
Gr.
Matthijs
On Sun, Apr 11, 2010 at 05:52:16PM +0200, Matthijs Kooijman wrote:
Hi Guido,
I do like this approach but I'm a bit worried about git-import-orig
becoming non interactive. Maybe it'd help to add a generic
Hi Matthijs,
On Fri, Jan 29, 2010 at 12:13:26PM +0100, Matthijs Kooijman wrote:
If there is no debian/changelog to find the source package name, and/or
the upstream version was not given on the commandline, ask the user for
them. The values guessed from the original tarball name are offered as
Hi Guido,
I do like this approach but I'm a bit worried about git-import-orig
becoming non interactive. Maybe it'd help to add a generic --interactive
variable. In case of interactive = False we'd not prompt for anything.
Hmm, but what do you do then? Fail with an error instead of prompting?
If there is no debian/changelog to find the source package name, and/or
the upstream version was not given on the commandline, ask the user for
them. The values guessed from the original tarball name are offered as
defaults to the user. Previously, this guessed version was used without
If there is no debian/changelog to find the source package name, and/or
the upstream version was not given on the commandline, ask the user for
them. The values guessed from the original tarball name are offered as
defaults to the user. Previously, this guessed version was used without
6 matches
Mail list logo
