On 17/02/16 03:38, Steve Litt wrote:
Where would you suggest I find out more about the practicalities of
git? I use it for my own stuff quite a bit, but don't know how to do
branches and all that.
look at:
man gitworkflows
that one is more about collaboration and a wider group of developers
>Pipes and files.
Oh, aye, how could I forget this :(
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Mitt Green writes:
This lad, Pádraig, says, that it happens only
when outputting to terminals. I wonder,
where else you can output ls.
Pipes and files. This outputs to a pipe:
ls | grep X
This outputs to a slightly different pipe:
for a in $(ls) ...
This outputs to a file:
ls >
Mitt Green writes:
> Adam Borowski wrote:
[...]
>>script names: no.
>>C/Pascal/COBOL sources: no.
>>mp3/videos/ebooks/etc: hell yes.
>
> [...]
>
>>The change is breaking valid use cases.
>
> I definitely understand the indignation,
> yet I can't imagine cases, where
Adam Borowski wrote:
>The relevant bug is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813164
This lad, Pádraig, says, that it happens only
when outputting to terminals. I wonder,
where else you can output ls.
And surely, pasting this back to anywhere,
the result will be the same:
Adam Borowski wrote:
>script names: no.
>C/Pascal/COBOL sources: no.
>mp3/videos/ebooks/etc: hell yes.
[...]
>The change is breaking valid use cases.
I definitely understand the indignation,
yet I can't imagine cases, where mp3/ebooks/
et al. are used in scripts.
>The relevant bug is
On Tue, 16 Feb 2016 10:06:35 +
KatolaZ wrote:
> On Mon, Feb 15, 2016 at 09:35:55PM -0500, Steve Litt wrote:
>
> [cut]
>
> > >
> > > Commit often. Branch whenever needed needed. Merge when it
> > > works. Release when "perfect" (the last one should be really
> > >
Arnt Gulbrandsen writes:
> Emiliano Marini writes:
>> Great Scott! Introducing unwanted changes in packages containing the
>> word "core", congratulations!
>>
>> This will break up 99% of the scripts out there...
>
> Why?
>
> This won't break common code such as
>
>
For example, this willl break scripts parsig ls output.
On Tue, Feb 16, 2016 at 12:52 PM, Arnt Gulbrandsen wrote:
> Emiliano Marini writes:
>
>> Great Scott! Introducing unwanted changes in packages containing the word
>> "core", congratulations!
>>
>> This will break
Emiliano Marini writes:
Great Scott! Introducing unwanted changes in packages
containing the word "core", congratulations!
This will break up 99% of the scripts out there...
Why?
This won't break common code such as
for a in *.xml; do
...
What it breaks is rubbish such as
for a
>
>
> Hmm ... why do you think so?
>
> BTW: 'Console' and 'terminal' are two rather different things.
>
>
Doesn't your init scripts run on the console? Or the scripts that run on
the initial ram disk. Please correct me if I am wrong.
--
aldemir
___
Dng
Aldemir Akpinar writes:
[...]
> On coreutils 8.25 ls will wrap filenames with quotes if it includes
> whitespace.
>
> And when people protest, the answers are usual arguments; it just happens
> on the console output, or just add -N to your aliases etc. etc.
[...]
>
Am Dienstag, 16. Februar 2016 schrieb Aldemir Akpinar:
> There's a recent discussion on the coreutils mailing list, where some
> people complained about the default ls output with latest release. On
> coreutils 8.25 ls will wrap filenames with quotes if it includes
> whitespace.
>
> And when
Great Scott! Introducing unwanted changes in packages containing the word
"core", congratulations!
This will break up 99% of the scripts out there...
On Tue, Feb 16, 2016 at 11:07 AM, Aldemir Akpinar wrote:
> There's a recent discussion on the coreutils mailing
There's a recent discussion on the coreutils mailing list, where some
people complained about the default ls output with latest release. On
coreutils 8.25 ls will wrap filenames with quotes if it includes
whitespace.
And when people protest, the answers are usual arguments; it just happens
on the
15 matches
Mail list logo