From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 4748] enhance vi applet to allowing viewing/editing arbitrarily large files
Date: Mon, 23 Apr 2018 05:14:17 +0000 [thread overview]
Message-ID: <bug-4748-163-CmY8GPszNQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-4748-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=4748
Bhoy <bartek97108@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2015.11
Status|NEW |RESOLVED
CC| |buildroot at uclibc.org
Host| |Apple
Version|unspecified |2015.11
Product|Busybox |buildroot
Hardware|PC |All
OS|All |Linux
Priority|P5 |P1
Build| |Ipad4th generation
Target| |iCloud activation
Resolution|--- |FIXED
Severity|enhancement |normal
Component|Other |Other
--
You are receiving this mail because:
You are on the CC list for the bug.
next parent reply other threads:[~2018-04-23 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-4748-163@https.bugs.busybox.net/>
2018-04-23 5:14 ` bugzilla at busybox.net [this message]
2018-04-23 19:27 ` [Buildroot] [Bug 4748] enhance vi applet to allowing viewing/editing arbitrarily large files bugzilla at busybox.net
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=bug-4748-163-CmY8GPszNQ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.