From: ycollette.nospam@free.fr
To: git@vger.kernel.org
Subject: Re: Add a bugzilla website
Date: Fri, 15 Nov 2013 11:34:17 +0100 (CET) [thread overview]
Message-ID: <361384464.315129845.1384511657291.JavaMail.root@zimbra35-e6.priv.proxad.net> (raw)
In-Reply-To: <20131115135132.431d3e344dadee64e2be5127@domain007.com>
OK, thanks for these informations.
From a user perspective, having this volume of devel mails flooding all the bugs mail is very annoying.
And following the status of a bug and the history of this bug is very hard too.
The bugzilla approach is really useful for the user who is reporting bugs: all the bugs are tracked, you can see if a bug has been already filled and put some additional informations if necessary.
I will have a look at the JIRA thing.
YC
----- Mail original -----
De: "Konstantin Khomoutov" <flatworm@users.sourceforge.net>
À: "ycollette nospam" <ycollette.nospam@free.fr>
Cc: git@vger.kernel.org
Envoyé: Vendredi 15 Novembre 2013 10:51:32
Objet: Re: Add a bugzilla website
On Fri, 15 Nov 2013 10:40:47 +0100 (CET)
ycollette.nospam@free.fr wrote:
> And the conclusion is ? No bugzilla tool installed because somebody
> want to build a gitbased bugzilla thing ?
Well, no, the real answer is that for those who actually write code and
apply patches, an e-mail based workflow is simpler: Git has tools to
apply patches right from Unix mailboxes, so one is able to just save a
thread with the final patch series to a file and apply it. Some people
also prefer discussing patches inline -- in the same e-mail thread
the patch series being discussed had started.
I'm aware of at least one big project sporting the same approach
to handling bugs -- PostgreSQL.
But there was an announcement that an experimental JIRA instance has
been set up for Git [1]. I'm not sure what its current status is, but
you could look at it.
Also Git's mirror on github [2] supposedly provides for pull requests.
Again, not sure whether/how they're handled.
1. http://git-blame.blogspot.ru/2012/02/experimental-git-bug-tracker.html
2. https://github.com/git/git/
next prev parent reply other threads:[~2013-11-15 10:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1501110902.314721105.1384501257984.JavaMail.root@zimbra35-e6.priv.proxad.net>
2013-11-15 7:44 ` Add a bugzilla website ycollette.nospam
2013-11-15 8:53 ` Damien Wyart
2013-11-15 9:40 ` ycollette.nospam
2013-11-15 9:51 ` Konstantin Khomoutov
2013-11-15 10:34 ` ycollette.nospam [this message]
2013-11-15 10:50 ` Matthieu Moy
2014-01-08 9:24 ` David Aguilar
2013-11-15 17:27 ` Andrew Ardill
2013-11-15 19:19 ` Jonathan Nieder
[not found] ` <CADoxLGPnoo_fXsQXE2jb_H4Otf9eRWsN=nQP9smhPbt20H-72Q@mail.gmail.com>
2014-01-13 1:06 ` Fwd: " Stefan Saasen
2013-11-15 22:57 ` brian m. carlson
2013-11-18 7:37 ` ycollette.nospam
2013-11-18 12:40 ` Matthieu Moy
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=361384464.315129845.1384511657291.JavaMail.root@zimbra35-e6.priv.proxad.net \
--to=ycollette.nospam@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).