From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: BTS for GRUB 2 (Re: BTS overhaul)
Date: Mon, 17 Dec 2007 08:10:53 +0100 [thread overview]
Message-ID: <200712170810.53995.okuji@enbug.org> (raw)
In-Reply-To: <20071216110235.GA7069@thorin>
On Sunday 16 December 2007 12:02, Robert Millan wrote:
> Another question is, how will we do context reply for patches? The BTS
> doesn't seem to easily allow this. Maybe we could followup on our replies
> via bug-grub ? But a problem with that is that it'll be hard to see the
> full context of a discussion when browsing bugs.
This was exactly what I didn't like with (most) bug trackers...
Does the Patch Tracker provide any useful feature to this? When I looked at
this, it was no different from the Bug Tracker, so I simply disabled it. But
this was some years ago.
> Another problem is that submitter is likely not subscribed to bug-grub
> (does the message you get when trying to write there without being
> subscribed say you have to subscribe, or that you have to wait for someone
> to process your mail (which won't happen) ?).
It might be possible to configure the mailman to push through email from
savannah.
Okuji
next prev parent reply other threads:[~2007-12-17 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 12:01 BTS overhaul Robert Millan
2007-12-12 14:37 ` Robert Millan
2007-12-12 16:43 ` Bean
2007-12-12 16:51 ` Jordi Mallach
2007-12-15 10:53 ` Robert Millan
2007-12-15 13:14 ` Marco Gerards
2007-12-16 18:36 ` Jordi Mallach
2007-12-14 22:04 ` Yoshinori K. Okuji
2007-12-15 22:43 ` BTS for GRUB 2 (Re: BTS overhaul) Robert Millan
2007-12-16 10:27 ` Vesa Jääskeläinen
2007-12-16 11:02 ` Robert Millan
2007-12-16 11:14 ` Robert Millan
2007-12-16 11:22 ` Vesa Jääskeläinen
2007-12-16 16:28 ` Robert Millan
2007-12-17 7:10 ` Yoshinori K. Okuji [this message]
2007-12-17 7:05 ` Yoshinori K. Okuji
2008-01-23 12:30 ` Marco Gerards
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=200712170810.53995.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.