Applied, thanks!
Janneke Nieuwenhuizen, le mer. 04 déc. 2024 19:10:32 +0100, a ecrit:
> * README: New file, documenting dependencies and development build.
> ---
> README | 43 +++
> 1 file changed, 43 insertions(+)
> create mode 100644 R
* README: New file, documenting dependencies and development build.
---
README | 43 +++
1 file changed, 43 insertions(+)
create mode 100644 README
diff --git a/README b/README
new file mode 100644
index ..425869de
--- /dev/null
+++ b/README
If the code is really dead, I agree with both courses of action.
Andrea
Hello,
Andrea Monaco, le sam. 02 oct. 2021 19:38:48 +0200, a ecrit:
> I just read on the Hurd Hacking Guide that libtreefs is defunct. Is it
> still true?
I don't know anything about libtreefs. I guess hhg is the best advice on
this :)
I wonder if we shouldn't just remove the directory? The hhg
October 3, 2021 3:19 PM, "Andrea Monaco" wrote:
> diff --git a/libtreefs/README b/libtreefs/README
> new file mode 100644
> index ..49477e93
> --- /dev/null
> +++ b/libtreefs/README
> @@ -0,0 +1 @@
> +libtreefs was never finished and is not developed an
diff --git a/libtreefs/README b/libtreefs/README
new file mode 100644
index ..49477e93
--- /dev/null
+++ b/libtreefs/README
@@ -0,0 +1 @@
+libtreefs was never finished and is not developed anymore.
+It should probably be ignored for all purposes.
October 2, 2021 1:40 PM, "Andrea Monaco" wrote:
> Hello,
>
> I just read on the Hurd Hacking Guide that libtreefs is defunct. Is it
> still true?
>
> If that's the case, could we please add a README file in the directory
> that says just that? Perhaps
Hello,
I just read on the Hurd Hacking Guide that libtreefs is defunct. Is it
still true?
If that's the case, could we please add a README file in the directory
that says just that? Perhaps something like "libtreefs was never
finished and is not maintained. It should probably be i
Hi,
On Tue, Sep 29, 2009 at 07:59:06AM +0200, Arne Babenhauserheide wrote:
> Maybe it would help testing to have a README in the new LiveCD which
> says, which commandline commands to use to test the translators (down
> to simple copy paste) - including a list of interesting translator
t; Closed
___
Follow-up Comment #2:
I just installed the following:
#v+
2006-11-17 Constantine Kousoulos <[EMAIL PROTECTED]>
Thomas Schwinge <[EMAIL PROTECTED]>
* i386/README-Drivers: Move most of the text into...
* doc/ma
URL:
<http://savannah.gnu.org/bugs/?18010>
Summary: GNU Mach: update i386/README-Drivers and
doc/mach.texi
Project: The GNU Hurd
Submitted by: tschwinge
Submitted on: Sunday 10/15/06 at 17:33
Category: GN
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
Here is a patch for this.
ChangeLog
2004-02-27 Alfred M. Szmidt <[EMAIL PROTECTED]>
* README, INSTALL: Changed [EMAIL PROTECTED]' to [EMAIL PROTECTED]'
proc/ChangeLog
2004-02-27 Alfred M. Szmidt <[EMAIL PROTECTED]>
* host.c (rebuild_uname): Changed
Ignore this message, my MUA accidently sent it for some odd reason.
The real message is the one that includes the diff for
release/dist-README.
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
Here is a patch for this.
ChangeLog
2004-02-27 Alfred M. Szmidt <[EMAIL PROTECTED]>
* README, INSTALL: Changed [EMAIL PROTECTED]' to [EMAIL PROTECTED]'
proc/ChangeLog
2004-02-27 Alfred M. Szmidt <[EMAIL PROTECTED]>
* host.c (rebuild_uname): Changed
Hi!
Hi, I think [srchurd]/README contain wrong bug report address. README
refer mail lists [EMAIL PROTECTED] and [EMAIL PROTECTED]
If I correct understand, for now there are [EMAIL PROTECTED] and
[EMAIL PROTECTED] mail lists used for bug repors.
Udachi,
e
16 matches
Mail list logo
