From: James Rowe <jnrowe@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: Git feature branch
Date: Thu, 28 Jan 2010 07:05:22 +0000 [thread overview]
Message-ID: <20100128070522.GA18649@ukfsn.org> (raw)
In-Reply-To: <20100127194149.GA23034@lapse.rw.madduck.net>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
* martin f krafft (madduck@madduck.net) wrote:
> also sprach micah anderson <micah@riseup.net> [2010.01.27.1124 +1300]:
> > Personally, I've found mailing lists that have patches sent to
> > them tends to totally kill the list for anything else. It seems
> > a bit weird to use Debian's bug tracker for a non-Debian native
> > program (but using it for the Debian package of notmuch does make
> > sense). I am not so familiar with Roundup, patch queue trackers or
> > patchwork to have anything to say about those.
>
> patchwork integrates with the mailing list and slurps patches and
> related discussion and threads them into a webpage, where they can
> be workflow-managed.
>
> The Debian bug tracker has the benefit of being usable with e-mail
> (and this is notmuch we're developing, don't forget). The others are
> all exclusively web-based, with the exception of launchpad, AFAIK.
As I use some of the other options...
Roundup has command line and email interfaces. The email interface is
quite similar to debian's. I've never used a launchpad hosted project
so I can't compare it.
Google's codereview tool has a nice interface for collecting and
commenting on patches, but I suspect that suggestion will also meet with
a degree of friction. To me codereview feels like patchwork with
polish.
Both gitorious and github have commenting functionality built in.
Commenting on commits in a fork is as easy as opening the commit in
a browser. I use something along the lines of the following script to
open commits on github:
#! /bin/sh
BASE=$(git config remote.${2:-origin}.url | sed 's,git\(@\|://\)\([^:/]*\)[:/]\(.*\).git,http://\2/\3/commit,')
COMMIT=$(git rev-parse ${1:-HEAD})
sensible-browser ${BASE}/${COMMIT}
Using github or gitorious you can easily find and track forks from one
place as well, which makes discovering new work much easier. Github
even provides a pretty single page interface to the work going on in
other forks, gitorious requires a little more leg work to do the same
but not much.
For a couple of hosted projects we use at the office we email the
individual entries from http://github.com/$user/$project/comments.atom
to the mailing list so they're /forcibly/ seen by everybody :)
Thanks,
James
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-28 7:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 14:00 Git feature branch Sebastian Spaeth
2010-01-20 20:00 ` micah anderson
2010-01-22 8:09 ` Sebastian Spaeth
2010-01-22 8:50 ` Sebastian Spaeth
2010-01-22 21:10 ` Carl Worth
2010-01-25 21:32 ` martin f krafft
2010-01-26 0:46 ` sebastian
2010-01-26 22:24 ` micah anderson
2010-01-27 19:17 ` Ben Gamari
2010-02-24 18:58 ` Carl Worth
2010-01-27 19:19 ` Jameson Rollins
2010-01-27 19:41 ` martin f krafft
2010-01-28 7:05 ` James Rowe [this message]
2010-02-01 22:31 ` patchwork test instance (was: Git feature branch) martin f krafft
2010-02-02 11:38 ` Marten Veldthuis
2010-02-10 3:25 ` patchwork test instance martin f krafft
2010-02-10 8:49 ` David Bremner
2010-02-10 22:00 ` martin f krafft
2010-02-10 9:25 ` Sebastian Spaeth
2010-02-10 22:22 ` martin f krafft
2010-02-24 19:10 ` Carl Worth
2010-02-24 20:39 ` martin f krafft
2010-02-24 19:08 ` Carl Worth
2010-02-25 8:06 ` martin f krafft
2010-02-04 3:05 ` Git feature branch Carl Worth
2010-02-04 3:50 ` martin f krafft
2010-02-05 3:36 ` patchwork now auto-updates patches from Git (was: Git feature branch) martin f krafft
2010-02-04 3:58 ` Git feature branch Jameson Rollins
2010-02-24 19:13 ` Carl Worth
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100128070522.GA18649@ukfsn.org \
--to=jnrowe@gmail.com \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).