From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: "'Sascha Cunz'" <sascha-ml@babbelbox.org>
Cc: "'Marc Khouzam'" <marc.khouzam@gmail.com>, <git@vger.kernel.org>,
<szeder@ira.uka.de>, <felipe.contreras@gmail.com>
Subject: RE: [PATCH] Completion must sort before using uniq
Date: Fri, 23 Nov 2012 13:36:03 +0100 [thread overview]
Message-ID: <003c01cdc977$1a8a60e0$4f9f22a0$@schmitz-digital.de> (raw)
In-Reply-To: <2630847.8aaR79v5Od@blacky>
> From: Sascha Cunz [mailto:sascha-ml@babbelbox.org]
> Sent: Friday, November 23, 2012 1:26 PM
> To: Joachim Schmitz
> Cc: 'Marc Khouzam'; git@vger.kernel.org; szeder@ira.uka.de; felipe.contreras@gmail.com
> Subject: Re: [PATCH] Completion must sort before using uniq
>
> > I can't see the difference and in fact don't understand uniq's -u option al
> > all Linux man pages say: "only print unique lines", but that is what uniq
> > does by default anyway?!?
>
> From the german translation of uniq's man-page, you can deduct that "only
> print unique lines" actually means: "print lines that are _not repeated_ in
> the input".
>
> A short test confirms that. i.e.:
>
> printf "a\nb\nb\nc\n" | uniq -u
>
> gives:
> a
> c
Ah, OK, then I rest my case. Sorry for the noise.
next prev parent reply other threads:[~2012-11-23 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <002201cdc952$00159c90$0040d5b0$@schmitz-digital.de>
[not found] ` <CAFj1UpEMKq9zH3nbLwYrNZRmd52_KEcN5BBrzGg2jxCzd+fsbA@mail.gmail.com>
2012-11-23 12:15 ` [PATCH] Completion must sort before using uniq Joachim Schmitz
2012-11-23 12:26 ` Sascha Cunz
2012-11-23 12:36 ` Joachim Schmitz [this message]
[not found] <1353557598-4820-1-git-send-email-marc.khouzam@gmail.com>
2012-11-22 4:16 ` Marc Khouzam
2012-11-23 8:09 ` Joachim Schmitz
2012-11-23 8:21 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003c01cdc977$1a8a60e0$4f9f22a0$@schmitz-digital.de' \
--to=jojo@schmitz-digital.de \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=marc.khouzam@gmail.com \
--cc=sascha-ml@babbelbox.org \
--cc=szeder@ira.uka.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).