Re: New project members: jonesc

Welcome, Chris! B-D Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to keep uncommitted work in a git clone

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 -- they consist of creating a 40 byte file. "git add" to put stuff into git is

Re: Github user repos?

Dear Ryan, please delete my user repo https://github.com/macports/macports-user-mk I don’t need it and didn’t use is since ages. Thanks in advance. Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org

Re: How to handle MacPorts' handles in the future (including the email address connected to it)??

Hi Ryan, On 02 Nov 2016, at 23:49 , Ryan Schmidt wrote: > I'm confused about why you're confused or what you're talking about. :) > We've always provided @macports.org email forwarding for committers. You tell > us what handle you want, we set it up to forward to

Re: [macports-ports] 01/02: New port for wallet @1.3

Hi Ryan, On Sat, Nov 05, 2016 at 03:40:48AM -0500, Ryan Schmidt wrote: > You should not use newlines in notes, unless you actually want the > user to see a newline there, for example if you are starting a new > paragraph or are constructing a list of items. Thanks, fixed:

Re: How to keep uncommitted work in a git clone

Hi, The other thing to realise with git is commits are a lot cheaper, as in the first instance they are only to your local checkout. So if you have a bunch of ’this commit is just so I can save the current state of this branch and switch to another’ commits these can be squashed before you

Re: How to keep uncommitted work in a git clone

Hi, I did the svn->git translation myself at work in the recent past and went through exactly the same things as you are now. Git and Svn are very different in some regards and workflows that worked with svn simply do not with git. The ‘make all changes on master and commit only what I want

Re: [macports-ports] 01/02: New port for wallet @1.3

> On Nov 2, 2016, at 8:06 PM, Clemens Lang > wrote: > > Clemens Lang (neverpanic) pushed a commit to branch master > in repository macports-ports. > > > https://github.com/macports/macports-ports/commit/a2792f4120bbf7fc5b7f771930da83895fd504f1 > > commit

Re: How to keep uncommitted work in a git clone

> On Nov 5, 2016, at 3:07 AM, Mojca Miklavec wrote: > > On 5 November 2016 at 08:39, Ryan Schmidt wrote: >> On Nov 4, 2016, at 12:39 AM, David Bariod wrote: >> >>> Personnally, I would just commit such change. It is cheap, can be reworked >>> later and be ketp safe in a

Re: PR usage by people with commit access

On 5 November 2016 at 08:33, Ryan Schmidt wrote: > > Now that we've converted to GitHub, I am automatically receiving emails about > each pull request submitted to the MacPorts repositories, and each comment > that's made on them. I've tried to participate in some of those, providing > feedback

Re: How to keep uncommitted work in a git clone

On 5 November 2016 at 08:39, Ryan Schmidt wrote: > On Nov 4, 2016, at 12:39 AM, David Bariod wrote: > >> Personnally, I would just commit such change. It is cheap, can be reworked >> later and be ketp safe in a private remote repository in case of disaster. >> With git there are no reason to not

Re: How to keep uncommitted work in a git clone

On Nov 4, 2016, at 12:39 AM, David Bariod wrote: > Personnally, I would just commit such change. It is cheap, can be reworked > later and be ketp safe in a private remote repository in case of disaster. > With git there are no reason to not commit event not ready yet change set. Coming from a

Re: PR usage by people with commit access

> On Nov 4, 2016, at 1:09 PM, Sterling Smith wrote: > > > On Nov 4, 2016, at 10:50AM, Rainer Müller wrote: > >> On 2016-11-04 18:10, Ivan Larionov wrote: >> >>> * Ability to get a feedback / review from other project members. >>> >>> We use