Hi,
On Thu, Dec 10, 2009 at 03:17:44PM +0100, Patrick Schoenfeld wrote:
> On Sun, Mar 22, 2009 at 03:36:53PM +0100, Jim Meyering wrote:
> > >> http://www.mail-archive.com/bug-coreutils@gnu.org/msg14650.html
> > >>
> > >> I was waiting for an updated patch, but
> > >> as far as I can see, that ne
Hi,
I just realized that this is still open. Unfortunately
in the meanwhile I lost the git checkout in which I worked
on this, so I had to merge the changes from the borked
patch I sent to the mailing list.
On Sun, Mar 22, 2009 at 03:36:53PM +0100, Jim Meyering wrote:
> >> http://www.mail-archi
Patrick Schoenfeld wrote:
> On Sun, Mar 22, 2009 at 02:31:32PM +0100, Jim Meyering wrote:
>> Patrick Schoenfeld wrote:
>> > I just remembered that I wrote that patch a while ago.
>> > Its been a while since my copyright assignment got active, so you may
>> > want to commit the patch which I sent a
On Mon, Nov 17, 2008 at 11:25:09AM +0100, Jim Meyering wrote:
> Good idea.
> I've just added that link to HACKING.
Great :-)
> > Makes sense. But this isn't a strong requirement is it? I don't even
> > have access to all this operating systems ;)
>
> With google, there's no need for access to t
Hi,
On Mon, Nov 17, 2008 at 10:34:02AM +0100, Jim Meyering wrote:
> Hi again,
>
> Patrick Schoenfeld <[EMAIL PROTECTED]> wrote:
> > Hi Jim,
> >
> > On Fri, Nov 14, 2008 at 09:09:09PM +0100, Jim Meyering wrote:
> >> If you're serious about it, and can sign a copyright assignment,
> >> please look
Hi,
ehh.. forgotten to write about this one:
On Fri, Nov 14, 2008 at 09:09:09PM +0100, Jim Meyering wrote:
> - demonstrate --check --pedantic failing due to invalid first line
> (ensure it still processes following ones -- should it warn
> about each? or just the first?)
I do
Hi Jim,
On Fri, Nov 14, 2008 at 09:09:09PM +0100, Jim Meyering wrote:
> If you're serious about it, and can sign a copyright assignment,
> please look through the coreutils contribution/style guidelines
> http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=blob;f=HACKING;hb=HEAD
> and make the follo
Patrick Schoenfeld <[EMAIL PROTECTED]> wrote:
...
>> > I was a bit sceptic about this copyright assignment and wondered why the
>> > HACKING file does not include any link to [1]. Just as a suggestion
>>
>> What's [1] ?
>
> sorry, accidentally removed the link:
>
> http://www.gnu.org/licenses/why-a
[EMAIL PROTECTED] wrote:
> JM> It should process every line.
> JM> My question was whether to emit a diagnostic for each _malformed_ line,
> JM> or just for the first or maybe the first few.
>
> Like cmp(1) bail out if any trouble perhaps, but have options for fuller
> digging/reports. OK, never m
JM> It should process every line.
JM> My question was whether to emit a diagnostic for each _malformed_ line,
JM> or just for the first or maybe the first few.
Like cmp(1) bail out if any trouble perhaps, but have options for fuller
digging/reports. OK, never mind... I leave it in your hands.
__
Patrick Schoenfeld <[EMAIL PROTECTED]> wrote:
> ehh.. forgotten to write about this one:
>
> On Fri, Nov 14, 2008 at 09:09:09PM +0100, Jim Meyering wrote:
>> - demonstrate --check --pedantic failing due to invalid first line
>> (ensure it still processes following ones -- should it warn
Hi again,
Patrick Schoenfeld <[EMAIL PROTECTED]> wrote:
> Hi Jim,
>
> On Fri, Nov 14, 2008 at 09:09:09PM +0100, Jim Meyering wrote:
>> If you're serious about it, and can sign a copyright assignment,
>> please look through the coreutils contribution/style guidelines
>> http://git.sv.gnu.org/gitw
PS> Otherwise I'd like to hear the submitters opinion as well.
The submitter leaves it all in your hands as I am not as sharp as I
used to be. Thanks.
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreut
Patrick Schoenfeld <[EMAIL PROTECTED]> wrote:
> Tags 353911 + patch
> thanks
>
> Hi,
>
> I just gave this wishlist bug some attention and implemented an
> additional option --pedantic, -p which if given additional to the check
> command causes md5sum to exit with a non-zero exit code.
>
> Attached
On Wed, Feb 22, 2006 at 10:11:35AM -0800, Paul Eggert wrote:
I agree that the current behavior is confusing. I'd prefer it if any
improperly formatted line caused a nonzero exit status. Is there some
reason things are done the way that they are?
Presumably to dump e.g., a set of md5's in a re
Paul Eggert <[EMAIL PROTECTED]> wrote:
...
> I agree that the current behavior is confusing. I'd prefer it if any
> improperly formatted line caused a nonzero exit status. Is there some
> reason things are done the way that they are?
>
> At the very least there should be an option to cause an err
Dan Jacobson <[EMAIL PROTECTED]> writes:
> $ md5sum test/*|sed 1s/./Z/|>/dev/null md5sum -c --status -w -; echo $?
> md5sum: standard input: 1: improperly formatted MD5 checksum line
> 0
> $ md5sum test/*|sed 1s/./Z/|>/dev/null md5sum -c -; echo $?
> 0
> $ md5sum test/*|sed s/./Z/|>/dev/null md5s
Package: coreutils
Version: 5.93-5
Severity: minor
File: /usr/bin/md5sum
Tags: upstream
The docs indeed say "if no valid line is found, `md5sum' exits with
nonzero status." i.e., 9 bad lines are no big deal, all we need is
one good line and we pass the so-called "--check"!!:
$ md5sum test/*|s
18 matches
Mail list logo
