similar to: Why R should never move to git

On 24/01/2018 6:35 PM, G?bor Cs?rdi wrote: > When you create a branch for your bug fix, don't create it off the > previous fix. Create it off the original, forked state of the repo. Branches keepclass2 through to keepclass5 are my attempts to do that. As far as I can see they are all the same as keepclass, which was branched from the head of the master branch of my fork. > >

On 25/01/2018 2:57 AM, I?aki ?car wrote: > For what it's worth, this is my workflow: > > 1. Get a fork. > 2. From the master branch, create a new branch called fix-[something]. > 3. Put together the stuff there, commit, push and open a PR. > 4. Checkout master and repeat from 2 to submit another patch. > > Sometimes, I forget the step of creating the new branch and I

On 25/01/2018 6:49 AM, Dirk Eddelbuettel wrote: > > On 25 January 2018 at 06:20, Duncan Murdoch wrote: > | On 25/01/2018 2:57 AM, I?aki ?car wrote: > | > For what it's worth, this is my workflow: > | > > | > 1. Get a fork. > | > 2. From the master branch, create a new branch called fix-[something]. > | > 3. Put together the stuff there, commit, push and

When you create a branch for your bug fix, don't create it off the previous fix. Create it off the original, forked state of the repo. Are the two commits here your fixes? https://github.com/dmurdoch/manipulateWidget/commits/master Gabor On Wed, Jan 24, 2018 at 11:17 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > Lately I've been doing some work with the

For what it's worth, this is my workflow: 1. Get a fork. 2. From the master branch, create a new branch called fix-[something]. 3. Put together the stuff there, commit, push and open a PR. 4. Checkout master and repeat from 2 to submit another patch. Sometimes, I forget the step of creating the new branch and I put my fix on top of the master branch, which complicates things a bit. But you

You need to create a branch from the original master, if you do git log master then you'll see which commit that is: f735449d679686867e7d3ab70810b09e8cea6366 So create that branch off that and switch to the new branch: git branch keepclassx f735449d679686867e7d3ab70810b09e8cea6366 git checkout keepclassx Then do git log keepclass to see the id of the new commit that you want to put on top of

On 24/01/2018 7:04 PM, G?bor Cs?rdi wrote: > You need to create a branch from the original master, if you do > git log master > then you'll see which commit that is: f735449d679686867e7d3ab70810b09e8cea6366 > > So create that branch off that and switch to the new branch: > git branch keepclassx f735449d679686867e7d3ab70810b09e8cea6366 > git checkout keepclassx > >

On 25 January 2018 at 06:20, Duncan Murdoch wrote: | On 25/01/2018 2:57 AM, I?aki ?car wrote: | > For what it's worth, this is my workflow: | > | > 1. Get a fork. | > 2. From the master branch, create a new branch called fix-[something]. | > 3. Put together the stuff there, commit, push and open a PR. | > 4. Checkout master and repeat from 2 to submit another patch. | >

Hi Duncan! I think there are many users whose first experiences with git where frustrating, and trust me, many people here can relate to your pain. I can certainly say that I can. At first, git makes significant effort to become fluent in seemingly "simple" tasks. I can literally feel your pain right now. But this is the main downside of git: that it can be hard to learn. I overcame

On 25/01/2018 7:03 AM, I?aki ?car wrote: > 2018-01-25 12:20 GMT+01:00 Duncan Murdoch <murdoch.duncan at gmail.com>: >> On 25/01/2018 2:57 AM, I?aki ?car wrote: >>> >>> For what it's worth, this is my workflow: >>> >>> 1. Get a fork. >>> 2. From the master branch, create a new branch called fix-[something]. >>> 3. Put together

On 25/01/2018 7:44 AM, G?bor Cs?rdi wrote: > On Thu, Jan 25, 2018 at 12:34 PM, Duncan Murdoch > <murdoch.duncan at gmail.com> wrote: > [...] >> but that branch doesn't show up in the Github web site. > > It is right there: > https://github.com/dmurdoch/manipulateWidget/branches > >> Any suggestions? > > Personally I would suggest to call it

Hi Duncan, I can see that branch on your github. Remember that you have to reload the github page to see the latest additions to your repo. It doesn't do that automatically. Cheers Joris On Thu, Jan 25, 2018 at 1:34 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 25/01/2018 7:03 AM, I?aki ?car wrote: > >> 2018-01-25 12:20 GMT+01:00 Duncan Murdoch

Hi, Every package I try to install in R i get the same error "had non zero-exit status". I use Ubuntu 18.04.1 LTS how can i fix this? Thank you This shows up when I try install.packages("Rcmdr", dep=T) Error : package ?htmltools? was installed by an R version with different internals; it needs to be reinstalled for use with this R version ERROR: lazy loading failed for

2018-01-25 16:07 GMT+01:00 Duncan Murdoch <murdoch.duncan at gmail.com>: > On 25/01/2018 7:44 AM, G?bor Cs?rdi wrote: >> >> On Thu, Jan 25, 2018 at 12:34 PM, Duncan Murdoch >> <murdoch.duncan at gmail.com> wrote: >> [...] >>> >>> but that branch doesn't show up in the Github web site. >> >> >> It is right there:

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

Hi, We compiled and successfully installed OpenSSH 3.8.1p1 (or earlier version), but has false respond from lssrc -a command. Example error message as: openssh daemon itself - "opensshd tcpip inoperative" or other daemon - "0513-001 The System Resource Controller daemon is not active" We've installed the following filesets on several AIX servers

Hi, I have two Samba 4.12.3 DCs (eucalipto and aroeira) on a Debian Buster and a Windows 2008R2 DC (antares). Replication got broken: root at eucalipto:~# samba-tool drs replicate antares eucalipto DC=ad,DC=a1,DC=ind,DC=br ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed (8418, 'WERR_DS_DRA_SCHEMA_MISMATCH') ? File

Hello, I am using EC2 to launch several instances. On each instance, I perform the following commands yum -y install R (installs R-2.6) R CMD javareconf sleep 10 wget rpackage.tgz R CMD INSTALL rpackage.tgz Now, rpackage.tgz needs to be built with jni libraries. When the instance is fully up, i log in and check if rpackage was successfully installed and find out it wasn't. Running R CMD

am a NEW user to flac.installed flac on eac.tried to rip a cd using eac with flac as external compression.tried the 'wav' icontried the 'mp3' iconboth options saves the file as 'wav'thought eac will rip the cd in the 'flac' file format.is this a 2-step procedure?wherein eac to 'wav' and re-ripped on flac frontend?or is there a ripper with flac in it that

The formatting of the IO-APIC debug key info has niggled me for a while, and with the latest interrupt bug I am chasing, has finally motivated me to fix it. The attached patch causes all columns to line up, and removes the comma which served no purpose in combination with the spaces already present. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900,