There's a silly bug I put into 1.10: If more than one item is moved within the same commit and later this commit is merged to another branch, the conflict resolver will consider every item moved in this commit as a possible move destination for any of the moved items 😞

For instance, in the only reasonable option is number 4 and the resolver shouldn't even be showing a prompt.

Fixed in and hopefully in a patch release soonish...

spectacular, peaceful, beautiful
Moon eclipse + opposition to Mars (for some time indeed red)

Here' is how it looked from Poland,. And how we found it.. And why so many regrets that not memorised on any of our photos, eh :(

Bunch more. You can see the shadow moving away now, towards the top left, with the bottom right of the moon becoming brighter again.

#editbacklog - the "not much of a backlog and more straight from the oven" edition.

...because #Istanbul is having an acute case of a clear sky by some miracle.

Sony a6000, Samyang 135mm F.2.0 Istanbul #Turkey

Obviously a very detail crop.

Edited using #Darktable in #ubuntustudio

#artwithopensource #linuxartists #photo #photography #creativetoots #mastoart #moon #bloodmoon #lunareclipse #lunareclipse2018

Very bad quality, but if you zoom in two red smudges should appear. The larger one is the moon and the smaller one is Mars.

Show thread

Saw the blood moon, Mars, and the ISS from our rooftop tonight. 😃

I have gathered information on how to make Gnome's ask for usernames on , rather than showing a menu of "real names" to choose from.

1) Create file
/etc/dconf/profile/gdm with lines:


2) Create file /etc/dconf/db/gdm.d/00-login-screen with lines:


3) Run 'dconf update'

4) Run '/etc/rc.d/gdm restart'

I don't understand the dconf magic, but works for me.

g2k18 hackathon report: Kenneth Westerback on dhcpd(8) fixes, disklabel(8) refactoring and more

@Kensan “The Intel® CSME firmware for the following products is no longer supported. These products will not receive a firmware update: Intel® Core™ 2 Duo vPro™, Intel® Centrino™ 2 vPro™, 1st Generation Intel® Core™, 2nd Generation Intel® Core™, 3rd Generation Intel® Core™.” if these are no longer supported then why not open source them?

‘We don't offer support, but we can't let you fix it either.’ ― such business practices should be illegal.
(╯°□°)╯︵ ┻━┻

Here is an example of what this new cherry-picking merge behaviour in looks like:

A tree conflict occurs because after Subversion 1.7 was branched from trunk, svn's own main C file was renamed in trunk from "main.c" to "svn.c". With my change from today, the resulting tree conflict is now automatically resolved. Previously, the merge stopped after the step "Tree conflict on 'subversion/svn/svn.c':" with SVN complaning that it didn't know how to handle the merge 🙄

Show thread
Show older

The original server operated by the Mastodon gGmbH non-profit