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
> > considered with a pinch of salt :P).
>
> When a version is a release, don't you just give it
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
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 list, where some
> people complai
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 peopl
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.
[...]
> When this version hits the d
>
>
> 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 m
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 i
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 up 99% of the scripts out t
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 a in *.xml; do
> ...
Aldemir Akpinar writes:
[...]
>> BTW: 'Console' and 'terminal' are two rather different things.
>>
>>
> Doesn't your init scripts run on the console?
'The system console' is an I/O device the kernel and scripts started
during boot will use for "user interaction", ie, print output supposed
to be
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
> > > considered with a pinch of
On Tue, 16 Feb 2016 19:47:37 +1300
Daniel Reurich wrote:
> On 16 February 2016 3:35:55 PM NZDT, Steve Litt
> wrote:
> >When a version is a release, don't you just give it a tag?
> >
> Yes. But that is no excuse for not using private branches to develop
> on. If you have to revert a commit y
No idea, why they did it,
but anyway, who uses whitespaces in
names of scripts? I always get
rid of them even when naming
wallpapers.
Mitt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Emiliano Marini writes:
For example, this willl break scripts parsig ls output.
Will it?
I spent a few minutes looking for scripts that might be broken. I did find
one that acted on ls output, but it wasn't broken.
Arnt
___
Dng mailing list
Dng@l
On Tue, 16 Feb 2016 16:07:35 +0200
Aldemir Akpinar wrote:
> 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
On Tue, Feb 16, 2016 at 07:51:47PM +0300, Mitt Green wrote:
> No idea, why they did it,
> but anyway, who uses whitespaces in
> names of scripts? I always get
> rid of them even when naming
> wallpapers.
script names: no.
C/Pascal/COBOL sources: no.
mp3/videos/ebooks/etc: hell yes.
The change is
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
>https:
Wish to run an i386 Devuan alpha4 as a guest OS in VirtualBox's
current v5.0.14[1], and under an i386 Linux-distro host.
The Devuan download zone[2] currently lists the four possibilities
for this as
- devuan-jessie-i386-alpha4.box
- devuan-jessie-i386-alpha4.qcow2
- devuan-jessie-i386-alpha4-ne
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: unwanted
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 mp3/ebooks/
> et al. are us
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 > /tmp/
>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
On Tuesday, 16 February 2016, Steve Litt wrote:
> On Tue, 16 Feb 2016 16:07:35 +0200
> Aldemir Akpinar > wrote:
>
>
> My response is unresponsive to your question, aldemir, but this is
> something I've given lots of thought to in the past. I quote from the
> referenced web page:
>
> =
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
On 17/02/16 13:38, Simon Wise wrote:
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 collabor
25 matches
Mail list logo
