On Wed, Oct 15, 2014 at 12:10:42PM +0100, Dimitris Papastamos wrote:
> On Wed, Oct 15, 2014 at 12:29:13AM -0500, M Farkas-Dyck wrote:
> > I'm not sure, but some in this community are hacking morpheus [1],
> > which is much alike.
> >
> > [1] http://morpheus.2f30.org/
>
> The project is currently
Another easy one. One of the context lines will have to be updated in Makefile
to apply after the link(1) patch.
>From 99c822c371c0e51464b9093a66dd5c73e3fae8e2 Mon Sep 17 00:00:00 2001
From: Brandon Mulcahy
Date: Thu, 16 Oct 2014 17:15:16 -0400
Subject: [PATCH] Add logname(1)
---
Makefile | 1
---
Heyho,
there you go, pretty simple, but it was still missing so here you go.
--Markus
Makefile | 1 +
README | 1 +
TODO | 1 -
link.1 | 14 ++
link.c | 16
5 files changed, 32 insertions(+), 1 deletion(-)
create mode 100644 link.1
create mode
Hello,
On Thu, Oct 16, 2014 at 2:16 AM, Dimitris Papastamos wrote:
> I kind of like this particular implementation of test(1). Are there any
> obvious deficiencies compared to the sbase implementation?
I haven't found any but that doesn't mean they aren't there.
> I will have a look at it in m
On Thu, Oct 16, 2014 at 09:26:01AM +, k...@shike2.com wrote:
> From: "Roberto E. Vargas Caballero"
>
> ---
> Makefile |6 +-
> config.def.h |2 ++
> last.c | 59
> ++
> 3 files changed, 66 insertions(+), 1 delet
From: "Roberto E. Vargas Caballero"
$? is expanded to all the requisites that are newer than the current target,
so we can avoid update files that were not modified since last time
the library was built.
---
Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile
From: "Roberto E. Vargas Caballero"
---
Makefile |6 +-
config.def.h |2 ++
last.c | 59 ++
3 files changed, 66 insertions(+), 1 deletion(-)
create mode 100644 last.c
diff --git a/Makefile b/Makefile
index 3989a77.
On Wed, Oct 15, 2014 at 01:24:26PM -0700, Evan Gates wrote:
> After looking at the sbase TODO I threw together test(1). As far as I
> can tell it's POSIX compliant. I used the POSIX description[0] to
> write it. It exits 0 for true, 1 for false, and 2 for bad input. Let
> me know what's good and wh
Applied thanks!
Can you use git format-patch in the future? Also make sure that you use
tabs instead of spaces for indentation.
Generally speaking we use tabs for indentation and spaces for alignment.
Cheers,
sin
On Wed, Oct 15, 2014 at 08:35:46PM -0400, Jeffrey Picard wrote:
> Hey all,
>
> I was poking around at du recently and noticed it doesn’t support human
> readable output. This is pretty easy to add however, at least in a simple
> form which just rounds the number of bytes down to the nearest incr
10 matches
Mail list logo
