On Wed, Oct 22, 2014 at 7:51 PM, Brent Cook wrote:
>
>
>> I've been hunting around the past few days, and found not much. I
>> looked at the OpenSSH portable project, but the only Windows build it
>> seems to support is under the Cygwin runtime, which I cannot use for
>> various reasons.
>>
>
>
On Wed, Oct 22, 2014 at 3:07 PM, Michael B. Trausch <
m...@fortifiedtechsystems.com> wrote:
> Hello,
>
> I would like to contribute a port for the Microsoft operating systems
> so that LibreSSL can support these systems without the GPL'd Cygwin
> DLL being present on the system. OpenSSL works on
On Wed, Oct 22, 2014 at 4:02 PM, Ted Unangst wrote:
> On Wed, Oct 22, 2014 at 16:07, Michael B. Trausch wrote:
>
> > I have done a very ugly port that builds and works in the few
> > scenarios that I've tested with, but it's not complete as some
> > features (mostly the ones that allow disabling
On Wed, Oct 22, 2014 at 16:07, Michael B. Trausch wrote:
> I have done a very ugly port that builds and works in the few
> scenarios that I've tested with, but it's not complete as some
> features (mostly the ones that allow disabling at compile time) need
> more work to finish porting.
I think t
On Wed, 22 Oct 2014 21:57:14 +0200 Ingo Schwarze
wrote:
> > So the newline before the close-brace is required. Since the code
> > matches the spec, I think we should change the doc to match both of
> > them. Or is there some reason this extension is required?
>
> That would be the following pa
Hello,
I would like to contribute a port for the Microsoft operating systems
so that LibreSSL can support these systems without the GPL'd Cygwin
DLL being present on the system. OpenSSL works on them already, but
support for that was removed due to its apparent insecurity and
kludgyness.
I have
Hi,
Philip Guenther wrote on Wed, Oct 22, 2014 at 10:46:43AM -0700:
> That looks like a documentation bug to me. To quote the POSIX spec:
> --
> [2addr] {editing command
> editing command
> ...
> }
>
> Execute a list of sed editing commands only when the pattern space
> is selected. The
On Wed, Oct 22, 2014 at 1:25 AM, Ingo Schwarze wrote:
> OK?
> Ingo
Looks good to me
Philip
On Wed, 22 Oct 2014 10:46:43 -0700 Philip Guenther
wrote:
> On Wed, Oct 22, 2014 at 8:37 AM, Christopher Zimmermann
> wrote:
> > $ sed -e "{ y/o/u/ }"
> > sed: 1: "{ y/o/u/ }": extra text at the end of a transform command
> >
> > but this is allowed according to the manual:
> >
> > Function
On Wed, Oct 22, 2014 at 8:37 AM, Christopher Zimmermann
wrote:
> $ sed -e "{ y/o/u/ }"
> sed: 1: "{ y/o/u/ }": extra text at the end of a transform command
>
> but this is allowed according to the manual:
>
> Functions can be combined to form a function list, a list of sed
> functions se
Hi
$ sed -e "{ y/o/u/ }"
sed: 1: "{ y/o/u/ }": extra text at the end of a transform command
but this is allowed according to the manual:
Functions can be combined to form a function list, a list of sed
functions separated by newlines, as follows:
{ function
fun
Hi Philip and Frank,
Philip Guenther wrote on Tue, Oct 21, 2014 at 11:38:34PM -0700:
> On Tue, Oct 21, 2014 at 2:29 PM, Frank Brodbeck wrote:
>> today I stumbled upon a script (testssl.sh) which utilizes the \c escape
>> sequence for printf(1). As we are missing that escape sequence and - if
>>
i think arm is the last arch that lacks the full set of ops advertised
by the atomic_foo manpages.
this adds support for the lowest common denominator, which in our
tree is armv5. armv5 lacks the linked load and store conditional
opcodes that armv6 grew. it implements that atomic sequences by
usin
13 matches
Mail list logo
