tags 501991 fixed-upstream pending
thanks

also sprach Stefano Zacchiroli <[EMAIL PROTECTED]> [2008.10.13.2203 +0200]:
>   SAVED_BRANCH := $(shell git branch 2> /dev/null | grep '^*' | cut -f 2 -d' 
> ')
>   tg-export:

How's this?

piper:..pkg/topgit/topgit|master|% debian/rules tg-export
test -d debian/patches && rm -r debian/patches || :
tg export -b debian/locations,test-branch --quilt debian/patches
Exporting debian/locations
Exporting test-branch
Exported topic branch test-branch (total 2 topics) to directory debian/patches

> >  5. Update the branch (if needed):
> >       git add -f -u
> >       git add -f debian/patches
> >       git commit "Releasing ${VERSION}"

Why that?

I suggest the following steps now:

1. git checkout build
2. git merge master
3. ./debian/rules tg-export
4. git add debian/patches
5. git commit -m'preparing 0.5-1'
6. build, test, upload, tag ('debian/topgit-0.5-1')


The merge should take care of your first git-add call, and removing
debian/patches and re-adding it has the benefit to remove patches no
longer needed.

Anyway, please check out the current Git repo
(ssh://git.debian.org/git/collab-maint/topgit.git) and tell me what
you think.

The relevant commits are:

http://git.debian.org/?p=collab-maint/topgit.git;a=commitdiff;h=e3aeda0917e24d33cdaab95a17b2ccaced1475e2
http://git.debian.org/?p=collab-maint/topgit.git;a=commitdiff;h=f609666a07395f6eaf735ac27a9a2be0883419d9

-- 
 .''`.   martin f. krafft <[EMAIL PROTECTED]>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Reply via email to