search for: cherry

Dear R users, I was wondering if R has a built-in function doing the following : my_match(values_vector,lookup_vector) { for each value of values_vector : if value %in% lookup_vector, then value is unchanged else, value is changed the the closest element of lookup_vector, "closest" meaning "the one that would come just after if we sorted them using order()" } For example :

Tested with 'make check-release'. tests/parallel (in check-slow) failed, although it does regularly and that seems to be because of libvirt. Rich.

On 01/15/2020 05:03 PM, Reid Kleckner via llvm-dev wrote: > Tom Stellard told me to use `git cherry-pick -x`, and if you look at the release branches, you can see it is used, although the old style is used as well. I'm not sure what script is being used there. > I recommend updating the merge.sh script to use `git cherry-pick -x` and then deleting the merge-git.sh script. -Tom > On...

...m master via the history graph, you know you missed moving some release fixes into master. Part of release validation then simply does "git branch --contains <release>" and checks that "master" is in the output. There are various tools to attempt the same vaildation when cherry-picking commits from master to release, but they rely on metadata on the cherry-picked commit (like the commit message with cherry-pick -x) and are thus somewhat fragile. I don't know of any tools that verify that fixes made on master make it to the release branch though I'm sure they exis...

...ttle confused. To me "staging" means incremental development, >>> getting things integrated correctly, etc. The final merge to "mainline" >>> is little more than a formality. You don't really want each individual >>> commit from the local branch cherry-picked on-by-one to mainline, do >>> you? > >> Yes, I do. > > Why? Because I optimize for the code reviewer, not the patch submitter. -Chris

John McCall <rjmccall at apple.com> writes: >> git branch --contains <sha1>, on the other hand, will tell you. > > Of course, this doesn't actually help if you've cherry-picked commits > over to your branch (e.g. because it's a release branch). How is that different from SVN? If revision 1234 fixes a bug is some branch, and the last revision in your trunk is 2345, can you tell whether your trunk has this bugfix applied by looking at revision numbers? --...

...d. To me "staging" means incremental development, >>>> getting things integrated correctly, etc. The final merge to "mainline" >>>> is little more than a formality. You don't really want each individual >>>> commit from the local branch cherry-picked on-by-one to mainline, do >>>> you? >> >>> Yes, I do. >> >> Why? > > Because I optimize for the code reviewer, not the patch submitter. Ok, but that still doesn't answer the question. How does cherry-picking help the code reviewer? He or...

Hi Michael, Can you please cherry pick r195411 into release-3.4 to fix building on older OS X? Thanks, Jeremy commit e323506316cc3948bd801be537a723c308d8e2d4 Author: Michael Gottesman <mgottesman at apple.com> Date: Fri Nov 22 05:00:51 2013 +0000 [block-freq] Update data in test case to be unsigned long long to fix m...

Hi all, I have a very simple problem that I cannot seem to find the answer to. Consider the following toy dataset: x <- read.table(textConnection("V1 apples bananas cherries indv.1 7 8 4 3 indv.2 7 7 4 9"), header = TRUE) How would I change the column name of ONLY the first column, not the others? Surely I should not have to re-specify the names of ALL the columns -- e.g.,

Hi, I am sending this proposal to get feedbacks on how we could make the tagging of bug fixes and regressions more obvious. The idea is to provide easily accessible information to help deciding what to cherry-pick in a release branch. * Context * People shipping compilers based on LLVM may not completely align with the official releases of LLVM. Thus, the stabilization of each custom release may happen at different period of time. Because of that, release managers have to come up with their own strate...

...2023 at 9:04?AM Uwe Kleine-K?nig <u.kleine-koenig at pengutronix.de> wrote: > > hello Sean, > > On Wed, Jul 12, 2023 at 02:31:02PM -0400, Sean Paul wrote: > > I'd really prefer this patch (series or single) is not accepted. This > > will cause problems for everyone cherry-picking patches to a > > downstream kernel (LTS or distro tree). I usually wouldn't expect > > sympathy here, but the questionable benefit does not outweigh the cost > > IM[biased]O. > > I agree that for backports this isn't so nice. However with the split > appro...

...2023 at 9:04?AM Uwe Kleine-K?nig <u.kleine-koenig at pengutronix.de> wrote: > > hello Sean, > > On Wed, Jul 12, 2023 at 02:31:02PM -0400, Sean Paul wrote: > > I'd really prefer this patch (series or single) is not accepted. This > > will cause problems for everyone cherry-picking patches to a > > downstream kernel (LTS or distro tree). I usually wouldn't expect > > sympathy here, but the questionable benefit does not outweigh the cost > > IM[biased]O. > > I agree that for backports this isn't so nice. However with the split > appro...

Are any plans for an API that would allow ZFS commands including snapshot/rollback integrated with customer''s application? Thanks, Cherry

...st get the patch and remove the `llvm` on top of the paths, but that’s not a scalable approach. > > IIRC, the -p option of 'patch' is exactly for doing this. Would that simplify your use-case? > Yes, for a single patch that would work. If there is a way to do that also when `git cherry-picking` from monorepo to llvm-only it would be great. Francesco >> On 14. Nov 2019, at 22:12, Francesco Petrogalli via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hello, >> >> I am trying to access https://git.llvm.org/git/llvm to be able to cherry p...

On 5/19/23 18:31, Richard W.M. Jones wrote: > > For the series: > > Reviewed-by: Richard W.M. Jones <rjones at redhat.com> Thanks! Commit range 67647b883e13..569bd1dd29da. > > BTW it's usually possible to cherry pick across git repos, eg: > > $ git fetch ../libguestfs > $ git cherry-pick -x <hash> Hm, good to know, thanks! I didn't know you could use git fetch this directly. Minimally I would have expected having to add a file:// scheme remote, before the fetch. In retrospect, the...

On Jul 22, 2011, at 12:33 AM, Matthieu Moy wrote: > John McCall <rjmccall at apple.com> writes: >>> git branch --contains <sha1>, on the other hand, will tell you. >> >> Of course, this doesn't actually help if you've cherry-picked commits >> over to your branch (e.g. because it's a release branch). > > How is that different from SVN? It isn't, and of course "git cherry-pick -x" does make it very easy to preserve this information. I'm just saying that the use case of release branche...

Package: src:xen Version: 4.17.0+46-gaaf74a532c-1 Severity: important Two major bugs have shown with the release of new hardware from AMD. Since the new hardware is likely to become common during the life of Debian/bookworm, you may wish to grab them early: ad15a0a8ca2515d8ac58edfc0bc1d3719219cb77 x86/time: prevent overflow with high frequency TSCs Turns out the latest generation is fast enough

Now that we’re on the Git monorepo, is there an updated script for cherry-picking commits into the release branch? llvm/utils/release/merge.sh appears to still use SVN, and llvm/utils/release/merge-git.sh uses git-svn. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200116/5c791bd2...

...erent dial plan extensions from the using the AMI. Currently, as soon as I redirect one of the channels the other appears to be dropped and gets reorder tone (congestion, fast busy). I guess what I really need is a way to redirect one of the channels and hold on to the other. Thanks, Neil Cherry

...koenig at pengutronix.de> wrote: >>> >>> hello Sean, >>> >>> On Wed, Jul 12, 2023 at 02:31:02PM -0400, Sean Paul wrote: >>>> I'd really prefer this patch (series or single) is not accepted. This >>>> will cause problems for everyone cherry-picking patches to a >>>> downstream kernel (LTS or distro tree). I usually wouldn't expect >>>> sympathy here, but the questionable benefit does not outweigh the cost >>>> IM[biased]O. >>> >>> I agree that for backports this isn't so ni...