Bug#504073: Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-11-03 Thread Jari Aalto
Guido Günther <[EMAIL PROTECTED]> writes: > On Fri, Oct 31, 2008 at 11:25:43AM +0100, Guido Günther wrote: > >> On Fri, Oct 31, 2008 at 12:59:34PM +0300, Jari Aalto wrote: >> FEATURE REQUEST >> >> Could there be a new option --force-empty-commit that would: >> >> * Commit with message-only

Bug#504073: Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-11-03 Thread Guido Günther
On Fri, Oct 31, 2008 at 11:25:43AM +0100, Guido Günther wrote: > On Fri, Oct 31, 2008 at 12:59:34PM +0300, Jari Aalto wrote: > > Guido Günther <[EMAIL PROTECTED]> writes: > > > > >> FEATURE REQUEST > > >> > > >> Could there be a new option --force-empty-commit that would: > > >> > > >> * Commit

Bug#504073: Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-10-31 Thread Guido Günther
On Fri, Oct 31, 2008 at 12:59:34PM +0300, Jari Aalto wrote: > Guido Günther <[EMAIL PROTECTED]> writes: > > >> FEATURE REQUEST > >> > >> Could there be a new option --force-empty-commit that would: > >> > >> * Commit with message-only: "Imported (no changes)" > >> * mark the commit as usual

Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-10-31 Thread Jari Aalto
Guido Günther <[EMAIL PROTECTED]> writes: >> FEATURE REQUEST >> >> Could there be a new option --force-empty-commit that would: >> >> * Commit with message-only: "Imported (no changes)" >> * mark the commit as usual "upstream/version" > > I don't think we can create a new commit object with

Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-10-31 Thread Guido Günther
severity 504029 wishlist clone 504029 -1 -2 retitle -1 note the current branch after import failures retitle -2 importing identical tarballs with different versions should be possible thanks On Fri, Oct 31, 2008 at 10:54:42AM +0300, Jari Aalto wrote: [..snip..] > That the program leaves on "upst

Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-10-31 Thread Jari Aalto
Guido Günther <[EMAIL PROTECTED]> writes: >> $ git-import-orig --verbose --upstream-version=2007.01.01 >> ../fvwm-icons_2007.01.01.orig.tar.gz >> Run above command (C-c to abort) > > Where does this come from? Nothing important. One script that

Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-10-30 Thread Guido Günther
bts tag 50402 +moreinfo On Thu, Oct 30, 2008 at 07:19:45PM +0200, jaalto wrote: > I was trying to upgrade from new tar: > > $ git-import-orig --verbose --upstream-version=2007.01.01 > ../fvwm-icons_2007.01.01.orig.tar.gz > Run above command (C-c to abort) ^^

Bug#504029: git-buildpackage: Branch is left in upstream - Nothing to commit, nothing imported.

2008-10-30 Thread jaalto
Package: git-buildpackage Version: 0.4.40 Severity: normal I was trying to upgrade from new tar: $ git-import-orig --verbose --upstream-version=2007.01.01 ../fvwm-icons_2007.01.01.orig.tar.gz Run above command (C-c to abort) Upstream version is 2007.01.01 tar ['-C', '../tmpoKDrq