There's a silly bug I put into #SVN 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 https://paste.apache.org/yLOj the only reasonable option is number 4 and the resolver shouldn't even be showing a prompt.
Fixed in https://svn.apache.org/r1836968 and hopefully in a patch release soonish...
Freedesktop.org now running gitlab. A story by Daniel Stone https://www.fooishbar.org/blog/gitlab-fdo-introduction/
This includes moving the X.Org repositories.
#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.
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 https://undeadly.org/cgi?action=article;sid=20180726184322
@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.