Git development
 help / color / mirror / Atom feed
From: Corey Trager <ctrager@yahoo.com>
To: git@vger.kernel.org
Subject: Fw: [ANNOUNCE]  BugTracker.NET (FOSS) now supports git integration
Date: Sun, 25 Oct 2009 09:53:21 -0700 (PDT)	[thread overview]
Message-ID: <169557.95216.qm@web65401.mail.ac4.yahoo.com> (raw)
In-Reply-To: <87k4yj8ta3.fsf@sanosuke.troilus.org>


Right now it just recognizes a number at the very beginning of the commit message, but what I should do is make that configure.   That is, I'm using a regex to find the integer, so I can just make that regex be something that's easy to configure.  I'll get that done soon, maybe today.


----- Original Message ----
From: Michael Poole <mdpoole@troilus.org>
To: Corey Trager <ctrager@yahoo.com>
Cc: git@vger.kernel.org
Sent: Sun, October 25, 2009 9:03:48 AM
Subject: Re: [ANNOUNCE]  BugTracker.NET (FOSS) now supports git integration

Corey Trager writes:

> BugTracker.NET is a free, open-source, GPL,  ASP.NET bug tracking app.
> More info at http://ifdefined.com/bugtrackernet.html
>
> With the integration, if you do a commit like...
> git commit  -a -m "123 fixed the bug"
> ...then the hook script will link up the commit to bug 123.
>
> Here are screenshots of the Subversion integration, which looks pretty much like the git integration:
> http://ifdefined.com/doc_bug_tracker_subversion.html
>
> Feedback very welcome, good or bad.

Does it recognize bug IDs in the footer section of a commit message
(where Signed-Off-By and similar lines typically go)?

Michael Poole


      

      reply	other threads:[~2009-10-25 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 13:15 [ANNOUNCE] BugTracker.NET (FOSS) now supports git integration Corey Trager
2009-10-25 14:03 ` Michael Poole
2009-10-25 16:53   ` Corey Trager [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=169557.95216.qm@web65401.mail.ac4.yahoo.com \
    --to=ctrager@yahoo.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox