Comment Re:I look forward to trying it out (Score 1) 97
Nevermind, I figured it out, it's an issue with my hypervisor. Workaround here: https://forum.parallels.com/th...
it was unlikely that the "git master" branch name was influenced by BitKeeper, and that "master" was "fairly standard naming" for this sort of thing and "more likely to be influenced by the CVS master repository". Petr Baudis is apparently the person that came up with the use of "master" and "origin" in git, https://twitter.com/xpasky/sta...
Despite its historical use, Petr Baudis shows some signs of remorse:
I picked the names "master" (and "origin") in the early Git tooling back in 2005. [...] I have wished many times I would have named them "main" (and "upstream") instead.
Pet's twitter also cites an example of a non master/slave relationship (twitter):
[... ]"master" as in e.g. "master recording". Perhaps you could say the original, but viewed from the production process perspective.
However, master/slave was the terminology used for IDE "PATA" hard disk drives prior to the adoption of SATA in 2009.
If Gnome spearheads this change and other projects are to follow, the implications will be widespread, at least to developers. Branch renames often require clone/deletion which can make collaboration much more difficult.
This transition may be eased if tools such as git adopt helper tools to handle the renaming. GitHub has already made a statement that it's onboard with this effort.
(Michael Sweet) [...] We are not eliminating support for 20-year-old printers, we are just planning to move support for such printers to dedicated applications/services so that we don't have to drag around the 30+ year old PPD metadata that is preventing us from fully supporting modern (less than 10 year old) printers. [1]
For those not familiar with "raw" printing, it's a common technique for receipts, labels and even magnetic stripe cards that allows bypassing the printer driver and communicating using the devices native print control language. Many places also use "raw" for dot-matrix printers, which will also suffer the same fate.
(Michael Sweet) As for the future, this sort of queue won't be supported and you'll need a "printer application" that can handle IPP requests. By then I expect there will be a basic dot matrix application that supports plain text printing (in addition to raster) that you'll be able to use... [2]
Exactly what the "printer application" that Michael is referring to will look like has yet to be determined. For example, if a Zebra label printer is plugged into a USB port for printing using conventional means (e.g. Libre Office), it can also be access through its "raw" interface via command line, or alternately through a "raw" configuration from within CUPS. Some even use a dedicated Raspberry Pi as a "raw" print-server. Currently, Apple hides the "raw" configuration options from the macOS desktop but they are still available through the CUPS web interface. Both the "raw" option through the CUPS web interface as well as the command line options will be removed with this change. CUPS is also used on linux distributions — many still offering the "raw" configuration through the UI or setup wizard — which will take the upstream change. This "raw" option from both UI and command line is planned to be removed. How soon this will actually occur and how quickly this will interrupt industry printing from macOS, Linux and BSD is largely unanswered.
(Michael Sweet) Apple has been in contact with all of the popular printer vendors over the last 10 years to prepare them for this. Some have implemented support for IPP and common file formats, a few have not. As I've said repeatedly, raw print queues are going away. If there is a dedicated raw printing solution it will be separate from the usual CUPS commands (e.g. "rawprint -d queue filename" instead of "lp -d queue -o raw filename"). But the more likely solution is to allow Clients to send vendor PDL [as is][...] [3]
In cases where a project is no longer actively being maintained, SourceForge has in some cases established a mirror of releases that are hosted elsewhere. This was done for GIMP-Win.
Editor's note: Gimp is actively being maintained and the definition of "mirror" is quite misleading here as a modified binary is no longer a verbatim copy. Download statistics for Gimp on Windows show SourceForge as offering over 1,000 downloads per day of the Gimp software. In an official response to this incident, the official Gimp project team reminds users to use official download methods. Slashdotters may remember the last time news like this surfaced (2013) when the Gimp team decided to move downloads from SourceForge to their own FTP service.
Therefore, we remind you again that GIMP only provides builds for Windows via its official Downloads page.
Note: SourceForge and Slashdot share a corporate parent.
Hackers of the world, unite!
