Re: RFH: Where/How to setup RCS for new libfuse-ocaml package
- To: debian-ocaml-maint@lists.debian.org
- Subject: Re: RFH: Where/How to setup RCS for new libfuse-ocaml package
- From: Goswin von Brederlow <goswin-v-b@web.de>
- Date: Sat, 07 Mar 2009 10:13:03 +0100
- Message-id: <87sklphf1c.fsf@frosties.localdomain>
- In-reply-to: <20090306141200.GA25141@usha.takhisis.invalid> (Stefano Zacchiroli's message of "Fri, 6 Mar 2009 15:12:00 +0100")
- References: <877i38kor7.fsf@frosties.localdomain> <49ABF37B.7010504@glondu.net> <87k577g1sn.fsf@frosties.localdomain> <20090303095033.GA4437@usha.takhisis.invalid> <87zlg2aivm.fsf@frosties.localdomain> <20090303132524.GA17130@usha.takhisis.invalid> <871vtd5vxi.fsf@frosties.localdomain> <20090304141030.GA12245@usha.takhisis.invalid> <87myby92sg.fsf@frosties.localdomain> <20090306141200.GA25141@usha.takhisis.invalid>
Stefano Zacchiroli <zack@debian.org> writes:
> On Fri, Mar 06, 2009 at 02:52:31PM +0100, Goswin von Brederlow wrote:
>> - tag for release
>> - git push
>
> I haven't looked at your work-flow in detail yet, but just a technical
> comment to avoid we will remain without the needed stuff to build on
> git.d.o.
>
> That "git push" above should actually be two commands:
>
> - git push --all
> - git push --tags
>
> The former is needed to ensure you push all branches to alioth (or,
> instead of --all, the list of branches you want to push). The latter
> is needed to ensure you push your tags to alioth (yes, it is a git
> dumbness, reported upstream multiple times).
I noticed that too when i actualy tried it on a testrelease. Good catch.
> Also, note that the proper way of tagging is "git -a
> debian/1.2.3-4". If you use git-buildpackage --git-tag, it will do the
> right thing by default.
>
> Cheers.
git tag -a ... you mean.
Are git tags limited to the branch you tag in or are they global?
MfG
Goswin
Reply to: