Bug #58874 for Git-Repository: Documentation: HOW-TO Create a new repository incorrect

Sun Jun 27 15:37:12 2010 nomad [...] null.net - Ticket created

Subject:	Documentation: HOW-TO Create a new repository incorrect
Date:	Sun, 27 Jun 2010 21:36:52 +0200
To:	bug-Git-Repository [...] rt.cpan.org
From:	Mark Lawrence <nomad [...] null.net>

Hi, The create example from the documentation: perl -e ' use Git::Repository; my $r = Git::Repository->create(init => ".");' results in the following: usage: git-init [-q | --quiet] [--bare] [--template=<template-directory>] [--shared[=<permissions>]] at - line 2 Cheers, Mark. -- Mark Lawrence

Thu Jul 01 05:18:09 2010 book [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #58874] Documentation: HOW-TO Create a new repository incorrect
Date:	Thu, 1 Jul 2010 11:17:57 +0200
To:	Mark Lawrence via RT <bug-Git-Repository [...] rt.cpan.org>
From:	"Philippe Bruhat (BooK)" <book [...] cpan.org>

On Sun, Jun 27, 2010 at 03:37:12PM -0400, Mark Lawrence via RT wrote: Show quoted text

> > The create example from the documentation: > > perl -e ' > use Git::Repository; > my $r = Git::Repository->create(init => ".");' > > results in the following: > > usage: git-init [-q | --quiet] [--bare] > [--template=<template-directory>] > [--shared[=<permissions>]] at - line 2 >

You have a git version older than 1.6.5. "git init $dir" is only supported as from version 1.6.5. To create a git repository like this, you have to do: chdir $dir; # skip this if you want to init '.' my $r = Git::Repository->create('init'); I'll make a note in the documentation. -- Philippe Bruhat (BooK) Eliminate a problem before it eliminates you! (Moral from Groo The Wanderer #65 (Epic))

Thu Jul 01 05:18:10 2010 The RT System itself - Status changed from 'new' to 'open'

Fri Jul 02 05:09:33 2010 MLAWREN [...] cpan.org - Correspondence added

On Thu Jul 01 05:18:09 2010, BOOK wrote: Show quoted text

> You have a git version older than 1.6.5. > "git init $dir" is only supported as from version 1.6.5. > > To create a git repository like this, you have to do: > > chdir $dir; # skip this if you want to init '.' > my $r = Git::Repository->create('init'); > > I'll make a note in the documentation.

Fixed in git repository: commit 313e045026d6a6a0b354da1f61732c1c5f016e68 Author: Philippe Bruhat (BooK) <book@cpan.org> Date: Thu Jul 1 12:24:15 2010 +0200 Document git init behaviour changed in 1.6.5 RT #58874 by Mark Lawrence Wouldn't it be nice if a git commit would scan the commit message, and react based on the contents? For example if "fixed: RT#58874" was found then post the commit message back to the bug report, or even change the bug status. Know of anything like that? Would you find it useful if I hacked something up? -- Mark Lawrence

Thu Jul 08 16:21:40 2010 book [...] cpan.org - Status changed from 'open' to 'resolved'

Thu Jul 08 16:21:41 2010 book [...] cpan.org - Fixed in 1.05 added

Tue Jul 13 13:22:59 2010 Philippe.Bruhat [...] free.fr - Correspondence added

Subject:	Re: [rt.cpan.org #58874] Documentation: HOW-TO Create a new repository incorrect
Date:	Tue, 13 Jul 2010 19:22:49 +0200
To:	Mark Lawrence via RT <bug-Git-Repository [...] rt.cpan.org>
From:	"Philippe Bruhat (BooK)" <philippe.bruhat [...] free.fr>

On Fri, Jul 02, 2010 at 05:09:33AM -0400, Mark Lawrence via RT wrote: Show quoted text

> > commit 313e045026d6a6a0b354da1f61732c1c5f016e68 > Author: Philippe Bruhat (BooK) <book@cpan.org> > Date: Thu Jul 1 12:24:15 2010 +0200 > > Document git init behaviour changed in 1.6.5 > > RT #58874 by Mark Lawrence > > Wouldn't it be nice if a git commit would scan the commit message, and > react based on the contents? For example if "fixed: RT#58874" was found > then post the commit message back to the bug report, or even change the > bug status. > > Know of anything like that? Would you find it useful if I hacked > something up? >

I don't know of anything like that. It could be useful, but I guess everyone has their own way of documenting this (e.g. in the Changes file). Also, this would probably be done has a commit-hook. I would probably not use it, because I tend to commit more than what actually ends up on the public repo, and I wouldn't want to leak those meaningless changes to the bugtracker. I usually update the tickets from time to time, typically after a release appears in RT. -- Philippe Bruhat (BooK) None suffer so much in a war as those who strive to end it. (Moral from Groo The Wanderer #51 (Epic))

Tue Jul 13 13:23:00 2010 The RT System itself - Status changed from 'resolved' to 'open'

Tue Aug 10 15:22:56 2010 book [...] cpan.org - Status changed from 'open' to 'resolved'