On 2/21/08, Cameron Dale <[EMAIL PROTECTED]> wrote:
> As a temporary workaround, is there a way to unset export-dir on the
> command-line? Since I have it set in my ~/.gbp.conf file I would need
> to unset it for the special case of building a snapshot.
Never mind, I figured it out right after I
On 2/21/08, Guido Günther <[EMAIL PROTECTED]> wrote:
> Yes, this comes from then notion that export-dir means "build the last
> committed tree because I want a 100% clean build (to upload)" but
> snapshot means "I need a quick version to test with". I could make the
> two options incompatible b
Hi Cameron,
On Wed, Feb 20, 2008 at 12:03:36PM -0800, Cameron Dale wrote:
> This works fine, unless you have export-dir set to ../build-area/. Then gbp
> does
> an export of the current HEAD in step 4, which doesn't include my uncommitted
> changelog containing the snapshot. So you end up with a b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: git-buildpackage
Version: 0.4.13
Severity: normal
As I understand it, the workflow for using snapshots is:
1) make some changes
2) commit them
3) call git-dch --snapshot --auto to update the changelog (don't commit it)
4) call git-buildpackg
4 matches
Mail list logo
