On Sun, May 18, 2008 at 07:17:18PM -0400, Andres Mejia wrote:
On Sunday 18 May 2008 6:40:38 pm Joey Hess wrote:
Andres Mejia wrote:
git-import-orig does use what's supplied by the --upstream-branch option
or what is found in the gbp.conf files and that is what is passed on to
On Monday 19 May 2008 2:18:24 am Guido Günther wrote:
On Sun, May 18, 2008 at 07:17:18PM -0400, Andres Mejia wrote:
On Sunday 18 May 2008 6:40:38 pm Joey Hess wrote:
Andres Mejia wrote:
git-import-orig does use what's supplied by the --upstream-branch
option or what is found in the
On Mon, May 19, 2008 at 02:38:50AM -0400, Andres Mejia wrote:
I think it would be better if it called the tag object instead of the
upstream
branch name, since in the latter case, it will always fail since it's finding
a local upstream branch (refs/heads/upstream) and a remote upstream
On Monday 19 May 2008 3:08:32 am Guido Günther wrote:
On Mon, May 19, 2008 at 02:38:50AM -0400, Andres Mejia wrote:
I think it would be better if it called the tag object instead of the
upstream branch name, since in the latter case, it will always fail since
it's finding a local upstream
Hi Andres,
On Mon, May 19, 2008 at 03:14:58AM -0400, Andres Mejia wrote:
On Monday 19 May 2008 3:08:32 am Guido Günther wrote:
On Mon, May 19, 2008 at 02:38:50AM -0400, Andres Mejia wrote:
I think it would be better if it called the tag object instead of the
upstream branch name, since in
Andres Mejia wrote:
git-import-orig does use what's supplied by the --upstream-branch option or
what is found in the gbp.conf files and that is what is passed on to
pristine-tar. I suppose this is a problem with git-buildpackage. I've already
cloned this bug and assigned it to
6 matches
Mail list logo
