> But could you write the proper ChangeLog entries to explain not only why
> the change but also what change is made? See git log and the GNU Coding
> Style. The idea is that they help a *lot* when having to dig back what
> happened to a given function, to the use of a macro, etc.
Of course, here
Hello,
Joan Lledó, le mar. 07 août 2018 18:02:39 +0200, a ecrit:
> Here are some patches for the lwip translator. They solve minor problems I've
> found when working on our lwip library.
Thanks :)
But could you write the proper ChangeLog entries to explain not only why
the change but also what
Hello,
Justus Winter, le Thu 15 Aug 2013 09:45:27 +0200, a écrit :
> this is my updated patch series for the sysvinit package.
Perhaps you should already submit all these patches except
[PATCH 4/7] initscripts: add runsystem.sysv
which depends on the hurd changes?
Samuel
Quoting Samuel Thibault (2013-07-15 11:18:03)
> Hello,
>
> Justus Winter, le Tue 09 Jul 2013 10:46:43 +0200, a écrit :
> > this is a patch series for the sysvinit package. Comments are
> > welcome. Patches seven and eight are somewhat questionable, but I'd
> > propose the first six for inclusion.
Hello,
Justus Winter, le Tue 09 Jul 2013 10:46:43 +0200, a écrit :
> this is a patch series for the sysvinit package. Comments are
> welcome. Patches seven and eight are somewhat questionable, but I'd
> propose the first six for inclusion. Any hints how to send patches to
> the sysvinit maintainer
Pino Toscano, le Tue 26 Feb 2013 16:14:50 +0100, a écrit :
> Do they look okay? May I push them?
Please do.
Samuel
Applied, thanks!
Samuel
I haven't used the savannah patch manager and don't really plan to start
thinking about it. If it is useful to people sharing patches before they
can be committed, then they can use it however they please. I have mostly
ignored its notification emails because they are not easy to read quickly
and
> Please don't post just references to mailing list archives and
> expect me to take patches from there. Those are munged and I'm
> not going to deal with that. Just repost them.
How do you feel about patches in the savannah patch manager? In
the past, a fair amount of time has g
Peter Bruin wrote:
Hi,
I'm in the process of splitting my changes for the OSF Mach/PowerPC
port into multiple patches (one per subdirectory of the Hurd source
directory). I'm done with most of the Hurd libraries and a few other
subdirectories; the patches, including ChangeLog entries for the
fin
On Sat, Aug 09, 2003 at 05:55:22PM +0200, Peter Bruin wrote:
> subdirectories; the patches, including ChangeLog entries for the
> finished patches, are on http://huizen.dds.nl/~pjbruin/hurd/. I could
I have committed something equivalent to your fatfs patch, but using
and bswap_16/bswap_32 inste
> Can you split the patches up by features, rather than directories?
> For example, all changes to device_open in one patch, etc.
> This would be much better to manage and maintain.
I agree.
> > Almost all changes are between #ifdefs, so applying the patches (at
> > least the ones that have Chang
On Sat, Aug 09, 2003 at 05:55:22PM +0200, Peter Bruin wrote:
> I'm in the process of splitting my changes for the OSF Mach/PowerPC
> port into multiple patches (one per subdirectory of the Hurd source
> directory). I'm done with most of the Hurd libraries and a few other
> subdirectories; the patc
Peter Bruin <[EMAIL PROTECTED]> writes:
> I've put a couple of patches for glibc and the Hurd on
> http://huizen.dds.nl/~pjbruin/hurd/, together with a small bit of
> explanation. Some of the patches (libc-powerpc.patch, dl-start.S,
> {ext2fs,libports,libshouldbeinlibc,libstore}.patch) are reason
> "M. Gerards" <[EMAIL PROTECTED]> wrote:
>
> > On what kind of PPCs does it work now?
>
> As far as I know, only on a certain PowerMac 5500/225 ;-)
>
> It should work on any PPC which can boot the OSF Mach kernel, i.e. on which
> MkLinux runs (and maybe a couple more). You can find the kerne
"M. Gerards" <[EMAIL PROTECTED]> wrote:
> On what kind of PPCs does it work now?
As far as I know, only on a certain PowerMac 5500/225 ;-)
It should work on any PPC which can boot the OSF Mach kernel, i.e. on which
MkLinux runs (and maybe a couple more). You can find the kernel on (a mirror
o
On Thu, Jun 12, 2003 at 04:00:04PM +0200, M. Gerards wrote:
> > The ext2 file system uses little-endian order, whereas htons etc. convert
> > from
> > native to network (big-endian) byte-order. So using htons would give you
> > exactly the wrong result. (Actually, I didn't even think of using hto
> The ext2 file system uses little-endian order, whereas htons etc. convert
> from
> native to network (big-endian) byte-order. So using htons would give you
> exactly the wrong result. (Actually, I didn't even think of using htons,
> since
> I looked at the Linux code for ext2fs and copied the l
Marco Gerards <[EMAIL PROTECTED]> wrote:
> I had a really quick look at your patches, especially the ext2fs
> patch. I have a little (perhaps stupid) question about this patch. I
> usually use htons ntos, etc. for handling endianess. Was there a
> reason not to use these functions? I'm really happ
Peter Bruin <[EMAIL PROTECTED]> writes:
> I've put a couple of patches for glibc and the Hurd on
> http://huizen.dds.nl/~pjbruin/hurd/, together with a small bit of
> explanation. Some of the patches (libc-powerpc.patch, dl-start.S,
> {ext2fs,libports,libshouldbeinlibc,libstore}.patch) are reason
On Sat, Feb 26, 2000 at 02:35:37PM +0100, Mark Kettenis wrote:
>That looks fine, though you should match `*-*-gnu*' for the configuration.
>Mark Kettenis is in charge of gdb for hurd and will take care of getting
>the fix put into gdb.
>
> It is probably easier to not conditionalize
Date: Sat, 26 Feb 2000 03:22:21 -0500
From: Roland McGrath <[EMAIL PROTECTED]>
That looks fine, though you should match `*-*-gnu*' for the configuration.
Mark Kettenis is in charge of gdb for hurd and will take care of getting
the fix put into gdb.
It is probably easier to not con
That looks fine, though you should match `*-*-gnu*' for the configuration.
Mark Kettenis is in charge of gdb for hurd and will take care of getting
the fix put into gdb.
23 matches
Mail list logo
