develooper Front page | perl.perl5.porters | Postings from July 2019

Re: Transition from RT to GitHub [FAQ]

Thread Previous | Thread Next
From:
Craig A. Berry
Date:
July 15, 2019 17:33
Subject:
Re: Transition from RT to GitHub [FAQ]
Message ID:
CA+vYcVwqSsfSCh_G599qc2C+86nd1JbWkrxV53r0g8G3u_kAaQ@mail.gmail.com
On Mon, Jul 15, 2019 at 12:10 PM Abigail <abigail@abigail.be> wrote:
>
> On Sat, Jul 13, 2019 at 08:38:39AM -0500, Craig A. Berry wrote:
> >
> > That's a good solution for a release tarball.  What Yves is talking
> > about is the tarball that has the git describe output embedded for any
> > random commit, i.e., what you get when you click the "snapshot" link
> > next to any commit in our current gitweb interface.  This is based on
> > running:
> >
> > $ perl Porting/make_dot_patch.pl > .patch
> >
> > in a git checkout *before* generating the tarball.  This allows the
> > downloader to build without having git installed.  I think some
> > Test::Smoke configurations depend on that.
>
>
> I'm not very familiar with git hooks, so perhaps I'm just suggesting
> nonsense, but could this .patch file be generated with an appropriate
> git hook?

It's a good thought, but there don't appear to be any hooks on an
archive operation and as far as I can tell, GitHub does not allow
server-side hooks anyway.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About