On 09/06/15 09:27, Pierre Gaston wrote:
> Well it tries to execute the file and show the lines where it gets an
> error, it's a useful behavior when you try to write a script.
>
> If you have read access to these files and can run bash, you can print
> them anyway eg:
>
> bash -c 'echo "$(
> so it
On Tue, Jun 9, 2015 at 11:16 AM, Avinash Thapa
wrote:
> Hi, I'll report the bug via email only.
>
> In this, you are able to get the /etc/passwd file inside an error, this
> thing looks weird to me so I thought to report you this thing.
>
> Just write in your terminal
> bash -i '/etc/passwd'
On 06/08/2015 06:28 AM, Avinash Thapa wrote:
> Hello
>
> I have to report a bug related to bash.So, this is good place to report the
> bug ?
Yes. Also good is using the 'bashbug' script, typically installed
alongside 'bash', for reporting the bug with information that we often
find helpful.
--
Hello
I have to report a bug related to bash.So, this is good place to report the
bug ?
Kind & Best Regards,
Avinash Thapa
> > * Ability to link with patches. In fact, github allows submitters to attach
> > a patch, and admin can just merge it in with one click, provided there are
> > no conflicts.
>
> The number of issues we get with patches already attached are few. The
> number of patches that are applied verbatim,
On 2014-01-13 22:31:01 -0800, Yuri wrote:
> e-mail has quite a few vulnerabilities. Spam, impersonation, etc. In the
> system relying on e-mail, spam filter has to be present. And due to this you
> will get false positives and false negatives, resulting in lost information.
> On the opposite, login
On Tuesday 14 January 2014 01:31:01 Yuri wrote:
> On 01/13/2014 12:32, Eric Blake wrote:
> > A mailing list IS a bug reporting system. When something receives as
> > low a volume of bug reports as bash, the mailing list archives are
> > sufficient for tracking the status of
On 01/13/2014 12:32, Eric Blake wrote:
A mailing list IS a bug reporting system. When something receives as
low a volume of bug reports as bash, the mailing list archives are
sufficient for tracking the status of reported bugs. It's not worth the
hassle of integrating into a larger syst
On 2014-01-13 12:26:43 -0800, Yuri wrote:
> I noticed that bash is in absolute minority of projects not using any bug
> reporting system. Instead, users are directed to this ML to report bugs.
> It seems like it could have been very beneficial so that people could track
> the status o
> I noticed that bash is in absolute minority of projects not using any
> bug reporting system. Instead, users are directed to this ML to report bugs.
Also see: man bashbug
Maybe an RSS feed could help, like:
http://rss.gmane.org/gmane.comp.shells.bash.bugs
Peggy Russell
On 01/13/2014 01:26 PM, Yuri wrote:
> I noticed that bash is in absolute minority of projects not using any
> bug reporting system. Instead, users are directed to this ML to report
> bugs.
> It seems like it could have been very beneficial so that people could
> track the status of
I noticed that bash is in absolute minority of projects not using any
bug reporting system. Instead, users are directed to this ML to report bugs.
It seems like it could have been very beneficial so that people could
track the status of the issues.
Yuri
ermittent pain to me that I am not, and am in fact unlikely ever to
be, in a position to actually contribute anything useful to almost any
of the projects in which I am interested - much less all of the ones I
actually use.
And now a few words about the GNU bug reporting mailing lists...
The GNU b
Bob Proulx wrote:
> I saw that you had set Reply-To: back to the mailing list and I do not
> know why that reply message did not respect your reply-to header.
> For what it is worth I think it should have done so.
I changed it. I've been burned in the past (or at least received
complaints) when
more forward progress when we work together instead of
fighting among ourselves.
And now a few words about the GNU bug reporting mailing lists...
The GNU bug mailing lists are open and there is no expectation that
bug reporters are subscribed in order to post bug reports. This makes
bug r
15 matches
Mail list logo
