All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Paul Larson <plars@linuxtestproject.org>,
	kmacy@fsmware.com, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: make mkpatches broken
Date: Tue, 19 Apr 2005 16:37:51 -0700	[thread overview]
Message-ID: <4265964F.7010607@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3C44@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:

> I think there's still an outstanding question as to whther its possible
> to configure bugzilla to enable anonymous bug sumbissions (no login). If
> so, we'll go with bugzilla to enable crosslinking with other bugzillas.
> If not, I porpose to just go with the Trac server we already have.
> 
> Anyone know?

Unfortunately, I couldn't find a way to do that. Bugzilla
seems to require a user login (email/pw).  All of the
documentation also suggests so. The two bugzillas I've
worked with (OSDL's and IBM internal) are set up to
require a login.

You could set up a dummy login account and a default mailing list
as the email if needed, would that be sufficient for your
needs? From what I can see, it's important to be able to
exchange email with the submitter, so having it be a genuine
email is useful. Is an anonymous login a showstopper?
Is the issue supporting the submitter login accounts?

thanks,
Nivedita

  reply	other threads:[~2005-04-19 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 22:25 make mkpatches broken Ian Pratt
2005-04-19 23:37 ` Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-19 23:56 Ian Pratt
2005-04-20  0:05 ` Jeremy Katz
2005-04-20  0:14 ` Nivedita Singhvi
2005-04-20  0:21   ` Nivedita Singhvi
2005-04-19 18:38 Paul Larson
2005-04-19 18:51 ` Kip Macy
2005-04-19 19:10   ` Paul Larson

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=4265964F.7010607@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=kmacy@fsmware.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=plars@linuxtestproject.org \
    --cc=xen-devel@lists.xensource.com \
    /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.