zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
	"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Now real bug in RE: Bug report interface comments
Date: Tue, 4 Apr 2000 11:14:02 +0400	[thread overview]
Message-ID: <000901bf9e05$5ae363e0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <000801bf9e03$a1c424e0$21c9ca95@mow.siemens.ru>

Sorry for followup. The bug is is 103887. I tried to enter line that
looks like

mv BIC\ NMI

but '\' disappeared. I thought, it was copy'n'paste problem and entered
followup - but back slash was not there either!

Now, I call this a real bug - Adam, could you speak with sourceforge
folks on that matter?

-andrej

> -----Original Message-----
> From: Andrej Borsenkow [mailto:Andrej.Borsenkow@mow.siemens.ru]
> Sent: Tuesday, April 04, 2000 11:02 AM
> To: ZSH workers mailing list
> Subject: Bug report interface comments
>
>
> I tried to submit a (possible) bug, but what I do not like,
> that I have
> to have a logon there. Else bug comes from none. Normally, I have a
> field to enter mail address. It cannot be expected, that
> every user that
> wants to submit a bug report will get login - that means, you have no
> way to communicate with submitter.
>
> I presume, this bug manager is intended for the end users in the first
> place.
>
> -andrej
>
> Have a nice DOS!
> B >>
>
>


  reply	other threads:[~2000-04-04  7:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-04  7:01 Andrej Borsenkow
2000-04-04  7:14 ` Andrej Borsenkow [this message]
2000-04-08 15:28   ` bug in sourceforge backslash handling Adam Spiers
2000-04-04 19:31 ` Bug report interface comments Peter Stephenson
2000-04-04 20:56   ` Clint Adams

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='000901bf9e05$5ae363e0$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.dk \
    /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://git.vuxu.org/mirror/zsh/

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).