On Mon, Dec 06, 2010 at 03:34:02PM +0100, Sandro Tosi wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384287
Ahhh, thanks for the pointer (I missed this). So at least no additional
action is needed (except sending a patch).
> BTS is in english, and all bug reports have to be in englis
Quoting Alexander Reichle-Schmehl (alexan...@schmehl.info):
> If I remember correctly, that was discussed some years ago, and the
> outcome of the discussion was, that as our translation teams lack the
> ressources, non English speaking users should contact their respective
> -user-foo mailing lis
Andreas Tille writes ("Re: Reportbug not translated (Was: Bug#605892: please
state that mails will be publically archived)"):
> If backed up by a proper patch an automatic translation might make sense.
> What about some intermediate step like:
>
> The recipient of
On Mon, Dec 6, 2010 at 13:22, Andreas Tille wrote:
> On Mon, Dec 06, 2010 at 10:46:44AM +0100, Sandro Tosi wrote:
>> > Unfortunately, it will require translations though...
>>
>> Reportbug is not translated :)
>
> While the not translated fact makes things easier in the issue of the
> thread IMHO
Hi!
Am 06.12.2010 14:48, schrieb Andreas Tille:
>> The only way I can see this working would be to have a sort of staging
>> bts, where users could send their bugs in their mother tongue, and where
>> some i18n teams could translate and forward to the actual bts. That's a
>> long way before that
On Mon, Dec 06, 2010 at 02:31:12PM +0100, Mike Hommey wrote:
>
> Wouldn't a translated reportbug be an invitation for non-english bug
> reports? That would surely be helpful for users, but otoh, a maintainer
> who can't read the bug reports can't do anything for theses users...
If backed up by a
On Mon, Dec 06, 2010 at 01:22:19PM +0100, Andreas Tille wrote:
> On Mon, Dec 06, 2010 at 10:46:44AM +0100, Sandro Tosi wrote:
> > > Unfortunately, it will require translations though...
> >
> > Reportbug is not translated :)
>
> While the not translated fact makes things easier in the issue of th
On Mon, Dec 6, 2010 at 13:22:19 +0100, Andreas Tille wrote:
> While the not translated fact makes things easier in the issue of the
> thread IMHO reportbug should definitely be translated. I checked BTS
> about this but there is no such open bug asking for i18ned reportbug.
> Am I the only one w
On Mon, Dec 06, 2010 at 10:46:44AM +0100, Sandro Tosi wrote:
> > Unfortunately, it will require translations though...
>
> Reportbug is not translated :)
While the not translated fact makes things easier in the issue of the
thread IMHO reportbug should definitely be translated. I checked BTS
abo
On Mon, Dec 6, 2010 at 10:46:44 +0100, Sandro Tosi wrote:
> Dear Release Team, could you please state your opinion if this is
> something that should be targetting squeeze?
>
I would say no.
Cheers,
Julien
signature.asc
Description: Digital signature
Hi,
basically Stefano already described in his previous mail (not the one I'm
replying to now) what I think is sensible for reportbug: display just a short
note, nothing scary, nothing to accept. You accept by using reportbug, just
like it always has been.
On Montag, 6. Dezember 2010, Stefano
On Mon, Dec 6, 2010 at 10:32, Stefano Zacchiroli wrote:
> On Mon, Dec 06, 2010 at 10:23:40AM +0100, Sandro Tosi wrote:
>> I was thinking about a one-off acceptance question, the first time you
>> execute reportbug after the introduction of this alert (the result
>> will be writtent to ~/.reportbug
On Mon, Dec 06, 2010 at 10:23:40AM +0100, Sandro Tosi wrote:
> I was thinking about a one-off acceptance question, the first time you
> execute reportbug after the introduction of this alert (the result
> will be writtent to ~/.reportbugrc), just like:
>
> Bug reports are publicly archived on bu
Hi Zack & all other :)
On Mon, Dec 6, 2010 at 10:10, Stefano Zacchiroli wrote:
> I suggest to fix this bug, in reportbug, with a concise, non-scary, and
> yet very clear message like: "your bug report will be given a unique
> identification number and then stored publicly on the web at
> http://b
On Sat, Dec 04, 2010 at 02:46:39PM +0100, Sandro Tosi wrote:
> On Sat, Dec 4, 2010 at 14:35, Holger Levsen wrote:
> > please state prominently that bug reports will be be archived publically.
> Before considering where & how to add this alert, I really want to
> have a broader consensus from the d
Hi Sandro,
On Samstag, 4. Dezember 2010, Sandro Tosi wrote:
> > please state prominently that bug reports will be be archived publically.
> I know where this request is coming from but IMO this is kinda an
> over-reaction. Before considering where & how to add this alert
I wouldnt call/make it an
Hi Holger,
thanks for the bug report, but...
On Sat, Dec 4, 2010 at 14:35, Holger Levsen wrote:
> please state prominently that bug reports will be be archived publically.
I know where this request is coming from but IMO this is kinda an
over-reaction. Before considering where & how to add this
17 matches
Mail list logo
