Re: alternative for github clone with submodules

see https://github.com/macports/macports-ports/blob/master/python/py-pytorch/Portfile#L92 Chris > On 7 May 2020, at 1:34 pm, macpo...@parvis.nl wrote: > > i cannot find a way to do git clone --recursive >

10.15 builder slave lost

Hi All, Apologies if its known downtime, but in case it is not the 10.15 builder is down. https://build.macports.org/waterfall cheers Chris smime.p7s Description: S/MIME cryptographic signature

Re: Just another heads up / RFC --> Re: new naming scheme for llvm/clang will cause wreckage fyi

Hi, > On 23 Apr 2020, at 8:15 pm, Ken Cunningham > wrote: > > The suggested renaming of the clang/llvm/lldb ports to > > clang-10 > > instead of > > clang-10.0 > > going forward from clang-10 onwards will have repercussions in a number of > places, should it proceed, as per the PR. > >

Re: A currently unstable CI?

> No action necessary. Both builds failed because "Could not resolve host". > Unfortunately we see these types of network errors rather frequently from > Travis CI and we do not know how to get the Travis people to resolve it. It > does not appear to be a very good service. We also use the

Re: git submodules

HI, If there is really no way to get everything via a tarball, one way is to configure the port to fetch directly from git clone and not a tar ball, and then in a post-fetch block run the git submodule init. See eg. https://github.com/macports/macports-ports/blob/master/devel/ccls/Portfile

CLT needs reinstalling on 10.15 buildbot

Hi, I am seeing this warning in a number of builds on the 10.15 build bot Warning: cltversion: The Command Line Tools are installed, but MacPorts cannot determine the version. Warning: cltversion: For a possible fix, please see: https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt Could

Re: it might be useful to be able to enable specific configure commands only when running tests

Hi, All you need to do is make sure the deps are all installed *before* running the tests for the specific port in question. I do this with > sudo port install XYZ … > sudo port uninstall XYZ > sudo port install XYZ +test Chris > On 18 Jan 2020, at 11:37 pm, Ken Cunningham > wrote: > > It

Re: Undefined symbols for architecture x86_64 on jsonnet submission

> On 23 Nov 2019, at 4:39 pm, Steven Smith wrote: > > Thank you for all the helpful guidance! > > The latest commit shows a working build. Here’s a working Portfile: > >

Re: Undefined symbols for architecture x86_64 on jsonnet submission

> On 23 Nov 2019, at 1:56 pm, Steven Smith wrote: > > Per https://guide.macports.org/#reference.phases.installation.list-modifiers > , > I’ll try starting with a blanket -delete of everything, try to get to the >

Re: Undefined symbols for architecture x86_64 on jsonnet submission

> On 23 Nov 2019, at 12:29 pm, Steven Smith wrote: > > This is a 100% MacPorts default flags or env issue, and nothing to do with > Google’s upstream repo or code. > > First, the repo’s make command works on macOS > >: >

Re: keeping software forks under MacPorts repo?

> On 9 Nov 2019, at 5:24 pm, Ken Cunningham > wrote: > > > >> On Nov 9, 2019, at 9:06 AM, Ryan Schmidt wrote: >> >> On Nov 9, 2019, at 11:00, Mojca Miklavec wrote: >>> >>> But we would probably want to >>> prefix the repository names (something like "fork_qt", "fork_llvm") to >>> clearly

Re: keeping software forks under MacPorts repo?

> On 9 Nov 2019, at 5:06 pm, Ryan Schmidt wrote: > > On Nov 9, 2019, at 11:00, Mojca Miklavec wrote: >> >> But we would probably want to >> prefix the repository names (something like "fork_qt", "fork_llvm") to >> clearly distinguish them from our main repositories. > > I wouldn't

10.15 builder offline ?

Looks like the 10.15 builder has gone down ? https://build.macports.org/waterfall Chris smime.p7s Description: S/MIME cryptographic signature

Re: OpenBLAS fixed in Xcode 11.2

Hi, Good to hear. However, Xcode 11.2 has not fixed everything, as x265 still seg. faults when build with clang from Xcode 11.2. cheers Chris > On 1 Nov 2019, at 12:49 am, Jack Howarth > wrote: > > Although it wasn't fixed in Xcode 11.2 beta 2, the -fcheck-stack issues > with

Re: replacing OpenGL with MoltenVK

> Chris, > I thought that MoltenVK was designed to be backward compatible with the > OpenGL data structures and calls. If so, shouldn't having new variants of the > mesa packages that link against the MoltenVK libraries instead of the macOS > OpenGL framework decouple the MacPorts X11

Re: replacing OpenGL with MoltenVK

> On 21 Oct 2019, at 6:30 pm, Ryan Schmidt wrote: > > > > On Oct 21, 2019, at 12:19, Jack Howarth wrote: >> >>Are there any plans for using the MoltenVK package in MacPorts as a >> replacement for the macOS OpenGL support that is slated for depreciation? > > I haven't heard of any

Re: Pick up SDKROOT as the sysroot fallback.

https://github.com/macports/macports-ports/commit/1850136d289019f3b29a5b24d3ec8ef9b23913ee Chris > On 13 Oct 2019, at 5:49 pm, Kenneth F. Cunningham > wrote: > >> Chris, >> FYI, this has

Re: Pick up SDKROOT as the sysroot fallback.

Yes, I know. We need a version for the gcc 9.2.0 version/branch, and the master one does not apply directly. cheers Chris > On 13 Oct 2019, at 5:30 pm, Jack Howarth > wrote: > > Chris, > FYI, this has already been committed upstream. > >

Re: gcc/g++ failures after xcode11 update

Hi, Note the error is not specific to gcc. Macports clang has the same problem. > clang++-mp-8.0 -O3 ./main.cpp In file included from ./main.cpp:1: In file included from /opt/local/libexec/llvm-8.0/bin/../include/c++/v1/iostream:38: In file included from

Re: libraw updates because fetch gives 404

Just manually download it yourself, and place it where it expects, i.e. /opt/local/var/macports/distfiles/libraw the primary source is at https://www.libraw.org/data/ <https://www.libraw.org/data/> > On 26 Aug 2019, at 9:55 pm, Riccardo Mottola > wrote: > > Hi, >

Re: libraw updates because fetch gives 404

Hi, > On 26 Aug 2019, at 8:49 am, Riccardo Mottola via macports-users > wrote: > > Hi, > > since yesterday I am trying to update... but... > > Is something wrong with our mirrors? The mirrors themselves seem fine. Just looks like the 0.19.5 update dist file was never mirrored for some

pull request labels not being set

Hi All, Anyone know why GitHub no longer seems to be automatically setting labels on new pull requests ? https://github.com/macports/macports-ports/pulls ? Chris smime.p7s Description: S/MIME cryptographic signature

Re: [MacPorts] #58848: Error: Failed to build rust: command execution failed

Hi, > What I find puzzling: > > 1. As I did not change anything on my system, why did all the files download > correctly this time but not the last time? Any number of possible reasons. Transient network issues to some mirrors for instance. The mirrors used for downloads are not the same each

Re: 10.7 buildbot disk space issues

> On 14 Aug 2019, at 11:30 pm, Ryan Schmidt wrote: > > > > On Aug 14, 2019, at 08:28, Christopher Jones wrote: > >>> As you can see from the cleanup step's output, there was 21GiB of space >>> available when the build failed. >>>

Re: 10.7 buildbot disk space issues

> As you can see from the cleanup step's output, there was 21GiB of space > available when the build failed. > > https://build.macports.org/builders/ports-10.7_x86_64_legacy-builder/builds/108375/steps/cleanup/logs/stdio > > How much free space does it need? > I guess more than that…

Re: build failure - odd compiler selection

options fail and port default to the first in the fallback list, which just happens to be clang. I think the cxx11 PG needs to extend the whitelist it sets, to include some of the new macports clang options… Chris > On 5 Aug 2019, at 6:46 pm, Christopher Jones wrote: > > Hi All, > &

build failure - odd compiler selection

Hi All, Just trying to understand the build failure in https://build.macports.org/builders/ports-10.8_x86_64_legacy-builder/builds/99778/steps/install-port/logs/stdio port in

Re: [MacPorts] #58729: legacy-support missing futimens() (and utimensat)

> On 16 Jul 2019, at 6:15 pm, René J.V. Bertin wrote: > > On Tuesday July 16 2019 15:42:49 MacPorts wrote: > >> Perhaps we might consider a "best approximation" so that software builds >> at least, and works as best the OS can support. I am thinking that is (or > > AFAIK this is the main

Re: `port select python` and qtwebengine

Hi, >> However, the person who reported the error to me claimed he only used `port >> select` and didn't create the symlink himself. I didn't push him to know how >> nor did I try myself, but if indeed `port select` allows this calling it a >> "user error" is a bit unjust. You cannot expect

Re: URGENT -- massive merge commit on macports/macports-ports

Hi, Its a merge commit, i.e. the committer at some point pulled in changes to a branch which they subsequently pushed to master without rebasing. Its ‘OK’ in that its not a real commit. The changes you see in GitHub won’t really happen (if you look in detail they are commits already in

Re: Cross-compilers broken

Hi, The ports directly using isl where all rev-bumped. However I guess it was forgotten to also do those using the cross-compiler PG Oberon ~/Projects/MacPorts/ports > git grep ":isl" | grep "path:" _resources/port1.0/group/crossgcc-1.0.tcl: path:lib/pkgconfig/isl.pc:isl

Re: [macports-ports] branch master updated: libgccX: rev-bump to match gccX following isl update

h and every binary to see if anything changed in them or not. Chris > > -Marcus > >> On May 5, 2019, at 8:56 AM, Christopher Jones >> wrote: >> >> >> >>> On 5 May 2019, at 4:48 pm, Marcus Calhoun-Lopez >>> wrote: >>>

Re: [macports-ports] branch master updated: libgccX: rev-bump to match gccX following isl update

> On 5 May 2019, at 4:48 pm, Marcus Calhoun-Lopez wrote: > > Greetings. > > With different versions of isl, the builds of libgccX may be slightly > different, but if what is installed is *exactly* the same (see, e.g., > https://packages.macports.org/libgcc9/). If the builds differ, then it

Re: Wireshark, Qt5 and El Capitan

Hi, Just to finish up, as the fix seemed trivial (us the PG to set the deps) I have pushed an update doing just this. So update and try again. Chris > On 21 Apr 2019, at 5:23 am, Chris Jones wrote: > > Hi, > > I was curious, so I fired off a build using the buildbots, just to see what >

Re: fake azure pipeline failures

Hi, >> >> > > You have to click through a couple things in Azure, but it does have a > log available: > Thanks ! Could you briefly explain the steps to get there ? Honestly, I was clicking around for quite a while

fake azure pipeline failures

Hi, Can anyone caste any light on why the checks in https://github.com/macports/macports-ports/pull/3873 are failing ? I am pretty certain, as I discuss in the comments, that the port update in question builds fine across the board, so

Re: Buildbot failures on 10.11

> > The log says: > > > xcrun: warning: cache file > '/var/folders/b3/_c47r31s23q0mgj1jvy64bkwgp/T/xcrun_db' appears to be > corrupted (21, 2090430, 327680); resetting it > cache: 0x10217d000 > .magic: XR1L > .numEntries: 21 > .strTableSize: 2090430 >

Re: license query

the license. cheers Chris > On 7 Mar 2019, at 12:15 pm, Joshua Root wrote: > > On 2019-3-7 21:43 , Christopher Jones wrote: >> Hi All, >> >> I am looking to setup some new ports, that will provide in macports >> access to the Intel Math Kernel Library and headers

license query

Hi All, I am looking to setup some new ports, that will provide in macports access to the Intel Math Kernel Library and headers (for use by another port later on, PyTorch). The license for this is the Intel Simplifed Software license

Re: OSX 10.6 clang / llvm circular dependency

> On 8 Feb 2019, at 9:32 pm, Michael Dickens wrote: > > Adding in some debug printouts inside portconfigure.tcl, I think what's > happening is that when "libc++" is specified, somewhere inside > portconfigure.tcl the possible compilers to used gets pared down. Since I'm > not specifying one

Re: OSX 10.6 clang / llvm circular dependency

> On 8 Feb 2019, at 7:43 pm, Michael Dickens wrote: > > Updated; rebuilt the PortIndex. No different. I find the following very > curious. "cmake" depends on itself circularly, which just can't be good; and, > the internal cmake dependency has somewhat different dependencies compared > with

OSX10.7 buildbot build failed due to 'no space left on device'

Hi, I am seeing a build failure on OSX10.7 that looks like an issue with the buildbot.

Re: Q about a (new) portgroup file

> On 27 Jan 2019, at 12:17 pm, Eric F (iEFdev) wrote: > > Thanks Chris, > > > On 1/27/19 12:41 , Christopher Jones wrote: >>> So, I'd like to ask… Where to put it? >> >> The port group code lives in the same GitHub project as the ports. See >>

Re: Q about a (new) portgroup file

> On 27 Jan 2019, at 11:35 am, Eric F (iEFdev) wrote: > > Hi, > > While waiting on a PR and a ticket, I spent the weekend looking at file I > once started with. > > // From an earlier convo (w Ryan): > … since github.setup sets it for you; > >>> An off-topic question about

Re: Issues with compiler flags in gfortran

> On 22 Jan 2019, at 4:16 pm, Ken Cunningham > wrote: > > > On 2019-01-22, at 2:37 AM, Joshua Root wrote: > > >> >> I think this issue overall is covered by >> , and I agree with jeremyhu's >> assessment there. Personally I do not really

10.12 build bot offline ?

Hi, I’ve noticed that the 10.12 builedbot has been offline for a while now. https://build.macports.org/waterfall what’s up with it ? cheers Chris smime.p7s Description: S/MIME cryptographic signature

Re: macports rot

HI, I do not agree with your conclusions below. I see no evidence of macports ‘rotting’ in any way. Nor do the GitHub insight statistics, as far as they go, support anything of the sort. The decrease in use of trac since the move to GitHub is in my opinion completely understandable and OK, as

Re: Xcode configuration woes

> On 10 Nov 2018, at 11:02 pm, Ryan Schmidt wrote: > > On Nov 10, 2018, at 02:53, Vincent Habchi wrote: > >> Ryan, >> >>> I don't know why Apple is doing this to us. This contradicts what we >>> previously knew about how SDKs were meant to function. The SDKs are >>> supposed to be the same

Re: problems with MP version of gfortran

See https://github.com/macports/macports-ports/pull/2980 <https://github.com/macports/macports-ports/pull/2980> Chris > On 10 Nov 2018, at 7:13 pm, Christopher Jones > wrote: > > > >> On 10 Nov 2018, at 7:09 pm, Christopher Jones > <mailto:jon...@hep

Re: problems with MP version of gfortran

> On 10 Nov 2018, at 7:09 pm, Christopher Jones > wrote: > > Hi, > > cctools was updated recently, changing the default variants it was built > with. This caused issues with the gcc compilers, so those where rev-bumped > last week to adapt. > > The issue tho

Re: problems with MP version of gfortran

Hi, cctools was updated recently, changing the default variants it was built with. This caused issues with the gcc compilers, so those where rev-bumped last week to adapt. The issue though is users on 10.2+ who had cctools installed would have done so with the xcode variant installed. The

'Python' license distribution ?

Hi, I just noticed that the root6 port no longer seemed to be distributed in binary tarball form for the latest updates I pushed for it. Looking at the build logs it appears to be because of "root6" is not distributable because its dependency "py36-defusedxml" has license "python" which is

Re: mojave 32-bit compatible and universal builds

> On 4 Nov 2018, at 1:54 pm, Ryan Schmidt wrote: > > On Nov 4, 2018, at 01:41, Ken Cunningham wrote: >> >> I thought I’d try a 32-bit compatible installation of MacPorts today on >> Mojave as a proof-of-concept, so I made a new prefix under /opt/universal >> and set up macports in it. >>

Re: dealing with java opened SSL errors

> I don't know about java, but the python portgroup deliberately disables the > ability to download dependencies. We don't want ports to download things > except during the fetch phase. And if a port has dependencies on other ports, > it should declare them. It looks like py-tensorflow already

dealing with java opened SSL errors

Hi All, I am trying to update a couple of ports, bazel and py-tensorflow, that require recent Java JDKs (10+) to build using macports provided openjdk ports. I am running into the issue below ERROR:

Re: Issues with clock_gettime(CLOCK_REALTIME, ) pre macOS 10.13

Hi, > I have been pondering a good way to make it add the header definition > properly ( ? use specific headers such as string.h injected ahead of the > system search directory and "include_next", perhaps?) and also possibly to > make each definition selectable, or at least OS-version groups

Re: OT: Apple 64-bit changes

> On 20 Oct 2018, at 11:54 am, Randolph M. Fritz wrote: > > Thanks. So – what does that mean for a command line application? Or does it > make any difference at all? Depends what you mean, building or running ? The bottom line is the writing has been on the wall for 32 bit applications in

Re: Merging pull requests before 72 hours

> On 18 Oct 2018, at 9:25 pm, Ken Cunningham > wrote: > > > On 2018-10-18, at 1:18 PM, Christopher Jones wrote: >> >> Beyond the above, not really. If it is indeed agreed that some package >> version updates are allowed under the ‘minor’ tag, then I thin

Re: Merging pull requests before 72 hours

>> >> That is understood. Either we allow ‘minor’ version updates directly, and >> accept that there will always be disagreements on what this means exactly, >> and sometimes a ‘minor’ update will be made that turns out not to be so >> minor, or we don’t allow any version updates under the

Re: Merging pull requests before 72 hours

Hi, > On 17 Oct 2018, at 1:17 am, Rainer Müller wrote: > > On 2018-10-16 10:06, Chris Jones wrote: >> On 16/10/18 07:37, Leonardo Brondani Schenkel wrote: On 15 Oct 2018, at 11:18 pm, Chris Jones >>> hep.phy.cam.ac.uk> wrote: > On 15 Oct 2018, at 10:34 pm, Leonardo Brondani

Re: tenfourfox - should it be in the MacPorts repo?

> On 11 Oct 2018, at 6:51 pm, Ken Cunningham > wrote: > > > On 2018-10-11, at 10:38 AM, Christopher Jones wrote: > >> Hi, >> >> A couple other thoughts… >> >> What platforms do you see this being useful on ? I know that older >> pla

Re: tenfourfox - should it be in the MacPorts repo?

, for instance. This I guess might help to mitigate a bit that platforms that would require the ’strip7’ patch… ( Not important, but what does the 7 mean in strip7 ? ) Chris > On 11 Oct 2018, at 6:29 pm, Christopher Jones > wrote: > > Hi, > >> Apparently, gcc48 can pro

Re: tenfourfox - should it be in the MacPorts repo?

Hi, > Apparently, gcc48 can produce some zero-length N_SECTs that error out in the > default strip command but don't need to. Cameron made them warnings instead > (see below). We are reaching the limits of my knowledge about this issue > right about now … OK. Looking at that patch, because

Re: tenfourfox - should it be in the MacPorts repo?

Hi, Being ’niche’ in itself is no reason to not include something in MacPorts, so that shouldn’t be a concern. We have plenty of ‘niche’ ports already, which is partly what makes MacPorts better than the alternatives ;) If the new ports build ‘normally’ like any other, then why not have them

Re: Ports tree setup for development

Hi, I have a complete clone of the port tree, but just under my regular user account. Oberon ~/Projects/MacPorts/ports > git status On branch master Your branch is up to date with 'origin/master'. nothing to commit, working tree clean then, in your macports sources.conf, just point it at this

Re: ranlib: malformed objects on 10.6

Hi, I’ve seen similar in the past, and it normal results when the compiler used is too new for the toolkit you are using (for ar etc.) and is generating code the assembler cannot understand. Do you have cctools installed ? Try updating your build to use the toolkit that provides instead.

Re: GitHub PG livecheck failing for release/tags

https://trac.macports.org/ticket/56975 > On 15 Aug 2018, at 6:37 pm, Michael Dickens wrote: > > At least for me, the GitHub PG livecheck is failing for release/tags ... > like, all of them; it is not failing for commits. A quick search on the MP > GIT

Re: Darwin 9 PPC tester ?

Great thanks. I’m hopeful that libgcc is going to be OK, but if not please post a full log to the PR. It would be nice if libgcc-devel also built, but this is not so important at this point. I had to blacklist gcc-4.2 to get it to build on intel 10.6 (so fallback to MPs clang-3.4) but I am

Re: iTerm Upcoming Versions

Looking at https://github.com/macports/macports-ports/blob/master/aqua/iTerm2/Portfile The port is already limited to 10.12 or newer… I do still wonder if that couldn’t be extended by using the compiler black list

Re: iTerm Upcoming Versions

That sounds like it could be a compiler requirement (c++14 or something like that). If so its something that can be worked around in MacPorts by using a different (non Xcode) compiler… Chris > On 28 Jul 2018, at 10:05 pm, Mark Anderson wrote: > > Turns out I'm wrong, it will run 10.10+,

macOS10.14 testers ?

Hi, I am just curious, has anyone else signed up for the 10.14 beta and played with it and MacPorts ? I have been doing this myself, in a VM, and whilst we cannot discuss anything here on list, as per the NDA, I would be interested to in private share what I have found, as there are perhaps

Re: [macports-ports] branch master updated: grep: add new variant to install as ggrep

> On 30 Jun 2018, at 2:13 pm, Rainer Müller wrote: > > On 2018-06-30 08:39, George Plymale II wrote: >> Ryan Schmidt writes: >> >>> Do all of the ports that declare the dependency "bin:grep:grep" already >>> know that they should alternately look for a binary called "ggrep"? I don't >>>

Re: https fetch error on older (<10.9) OSX releases due to rejected protocol

t;https://trac.macports.org/ticket/51516#comment:19>> > > I > > Ken > > On 2017-10-18, at 12:39 PM, Christopher Jones wrote: > >> Hi, >> >> I just just been looking into a build failure on older OS in one set of >> python ports, pyXY-bleach, that

Re: Do the contributing rules apply just to non-committers?

> On 1 Oct 2017, at 6:53 pm, Ryan Schmidt wrote: > > > On Oct 1, 2017, at 12:41, Leonardo Brondani Schenkel wrote: > >> On 2017-09-27 20:36, Leonardo Brondani Schenkel wrote: >>> On 2017-09-27 20:18, Ryan Schmidt wrote: Most projects on SourceForge organize

Re: Building port from GitHub commit rather than tag

Thanks, not sure how I missed that ... > On 27 Sep 2017, at 7:34 pm, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On Sep 27, 2017, at 13:14, Christopher Jones wrote: > >> I am trying to update a port, where I need to use a GitHub commit ID rather >

Building port from GitHub commit rather than tag

Hi, I am trying to update a port, where I need to use a GitHub commit ID rather than a tag to pick up a fix committed after the release for Xcode 9 support. I have done this in the past with code like # Use git commit to work around Xcode 9 issue github.setuproot-mirror root

libgcc - build failure on macOS 10.13

Hi, I know the new OS is only just out, but I just submitted https://trac.macports.org/ticket/54900 which details a build failure of libgcc on this platform. Port has no maintainer so thought I would post here. Any ideas ? cheers Chris

Re: gcc & libgcc 6/7/8

Hi, In my opinion libgcc should be based on the latest stable gcc release, which is now gcc7. Right now, if I try and install gcc 7 I get > Oberon ~ > sudo port install gcc7 > Portfile changed since last build; discarding previous state. > ---> Computing dependencies for gcc7 > Error: Can't

Re: Are macports builds prevented from accessing /dev/random ?

l J. Luke wrote: >> On Jun 13, 2017, at 4:57 PM, Christopher Jones <jon...@hep.phy.cam.ac.uk> >> wrote: >>> :info:build open('/dev/random'): Operation not permitted >>> >>> Now, this works outside. So I suspect the build is in some way prevent the >>&

Re: Criteria for picking compilers from fallback list ?

t 7:15 pm, Ryan Schmidt <ryandes...@macports.org> wrote: > >> >> On Dec 7, 2016, at 12:05 PM, Christopher Jones <jon...@hep.phy.cam.ac.uk> >> wrote: >> >> >>> On 7 Dec 2016, at 5:32 pm, Joshua Root <j...@macports.org> wrote: >>&

Re: Criteria for picking compilers from fallback list ?

> On 7 Dec 2016, at 5:32 pm, Joshua Root wrote: > > On 2016-12-8 04:24 , Chris Jones wrote: >> Hi, >> >> I'm working on an update to the root6 port, where the minimum compiler >> requirement has been increased in the latest release, such that I need >> to update the compiler

Re: GitHub migration complete

> On 9 Nov 2016, at 12:51 pm, René J.V. Bertin wrote: > > Hi, > > I've just managed (I think) to fork macports-ports via github.com, add it as > an additional remote to my working copy of the original, created a topic > branch in my fork and made a pull request from

Re: How to keep uncommitted work in a git clone

> On 5 Nov 2016, at 4:50 pm, Michael wrote: > > Keep in mind that there was one overall design goal of git: Whenever there > was more than one right way to do something, do the opposite of svn. > > That is not a joke or exaggeration. > > Branches in git are dirt cheap

<    1   2