search for: squashes

On 6/2/2016 1:48 PM, via llvm-dev wrote: > Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> writes: > >> Github has an automatic "squashed" mode for pull requests now, I >> haven't tested in practice but it may help. > IMHO squashed commits are a bad idea from a bisect perspective. One of > the great benefits of git is the easy of creating small,

On Thu, Jun 25, 2020 at 11:43 AM Nikita Popov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On Thu, Jun 25, 2020 at 11:22 AM Zachary Turner via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> What this means for LLVM is that everyone will have to completely stop using history rewriting operations. No more rebase, squash, amend, etc. > > This is also incorrect. Most

Just to clarify: All the LLVM incubator repositories have "enforce linear history" enabled. Neither "Squash and Merge" or "Rebase and Merge" results in a Merge commit in the git history. Steve On Fri, Sep 11, 2020 at 3:32 PM Hubert Tong < hubert.reinterpretcast at gmail.com> wrote: > On Fri, Sep 11, 2020 at 6:12 PM Renato Golin <rengolin at

On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > Hi Rusty, all > > > > I parked outstanding virtio patches here: > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next > > this way they are merged in linux-next as well. > > > > Rusty if you'll be

On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > Hi Rusty, all > > > > I parked outstanding virtio patches here: > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next > > this way they are merged in linux-next as well. > > > > Rusty if you'll be

On Fri, 11 Sep 2020 at 19:32, Hubert Tong via llvm-dev < llvm-dev at lists.llvm.org> wrote: > There seems to be a split between those who prefer to curate commits >> locally and present them in the PR (i.e. Method 3) as they are to be >> committed (i.e. squash/amend/etc from my workstation and push the result), >> and those who seem to feel that it is better to avoid

On Fri, Sep 11, 2020 at 6:53 PM David Blaikie <dblaikie at gmail.com> wrote: > Is there any observable difference between "Squash and Merge" or "Rebase > and Merge" when "enforce linear history" is enabled, then? > "Squash and Merge" will only generate one commit. > > On Fri, Sep 11, 2020 at 3:45 PM Stephen Neuendorffer via llvm-dev

> On Jun 2, 2016, at 11:03 AM, dag at cray.com wrote: > > Tim Northover via cfe-dev <cfe-dev at lists.llvm.org> writes: > >> On 31 May 2016 at 13:45, Mehdi Amini via lldb-dev >> <lldb-dev at lists.llvm.org> wrote: >>> Apparently I wasn't very clear: llvm and clang (and the others >>> projects) would be simple decoupled, individual git

The LLVM incubator projects have been using github PRs for reviews and so far haven't really seen any significant issues. The biggest confusion so far has not been with reviews but with the difference between "rebase and merge" and "squash and mere". We have used basically 3 different processes: Method 1: start a review with one commit on a new branch (typically in a

On Tuesday, 26. June, an LLVM Meetup will take place in Paris. We invite everybody interested in LLVM to join. o What is LLVM? LLVM is a collection of modular and reusable compiler and toolchain technologies. It is used as the base of many modern compilers such as clang (C/C++/Objective-C), GHC (Haskell), dragonegg (Ada, Fortran, ...), several commercial OpenCL compilers or RenderScript.

On Tue, 28 Jan 2020 at 16:09, David Greene <dag at cray.com> wrote: > The question is if everything is approved and the author does a final > cleanup as alluded to above, does that final cleanup also need to go > through review? We don't enforce that now, so I see no reason to start doing it. Phab reviews, once approved, can have last-minute modifications and direct commits.

Looks like we are better off sticking with the misaligned stat struct, to reduce the amount of virtio 1 specific code in balloon. So let's do it. Add a detailed comment to reduce the chance people copy this bad example. This also fixes a bug on BE architectures: tag should use cpu_to_le16, not cpu_to_le32. Acked-by: Cornelia Huck <cornelia.huck at de.ibm.com> Signed-off-by: Michael

So, I am starting to code this CAS block squashing test and I am wondering if this is something that would more likely extend open Solaris (it does require additional info in zfs metadata that is currently reserved space for future, ie zfs revision++) or if I should code against the FUSE tree where it would could be imported. What type of contribution style is open Solaris? Is zfs

Looks like we are better off sticking with the misaligned stat struct, to reduce the amount of virtio 1 specific code in balloon. So let's do it. Add a detailed comment to reduce the chance people copy this bad example. This also fixes a bug on BE architectures: tag should use cpu_to_le16, not cpu_to_le32. Acked-by: Cornelia Huck <cornelia.huck at de.ibm.com> Signed-off-by: Michael

Leading up to the upcoming orphan removal in EPEL, the EPEL Steering Committee is organizing a Bug Squashing Day. There are 3 main purposes to this day: 1. Identifying owners willing to take over orphaned packages 2. Bug triage, feedback, or fixing various bugs through patch submission, etc. 3. Last but not least, we'll be covering the testing of various packages which need feedback.

On Thu, Mar 23, 2023 at 12:50:49PM +0100, Christian Brauner wrote: > On Thu, Mar 23, 2023 at 07:43:04AM -0400, Michael S. Tsirkin wrote: > > On Thu, Mar 23, 2023 at 11:44:45AM +0100, Christian Brauner wrote: > > > On Thu, Mar 23, 2023 at 03:37:19AM -0400, Michael S. Tsirkin wrote: > > > > On Wed, Mar 22, 2023 at 01:56:05PM -0500, Mike Christie wrote: > > >

Hello just learned HowTo but R, reminded me with the way Perl does it but with much less on-line commands, R "AFAIK" has n, c, Q and where and cann't debug outside the {}. 1) is there a more versatile/flexable debugging method for R? I have saved 2 functions in an ASCII file "digfun". "getdata" function calls "squash" function and both use loops. In

Has anyone tried out reviewable.io yet? It integrates with GitHub pull requests, but provides a separate UI for doing the review which promises to fix a lot of the issues encountered with Github's review interface. Some of the things it claims to support which seem like important additions: - Tracking the resolved status of each discussion point - Rebasing a PR without losing review history.

On Thu, Apr 02, 2020 at 11:22:57AM +0800, Jason Wang wrote: > > On 2020/4/2 ??12:08, Michael S. Tsirkin wrote: > > On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > > > >From 9b3a5d23b8bf6b0a11e65e688335d782f8e6aa5c Mon Sep 17 00:00:00 2001 > > > From: Jason Wang <jasowang at redhat.com> > > > Date: Wed, 1 Apr 2020 22:17:27 +0800 >

On Thu, Apr 02, 2020 at 11:22:57AM +0800, Jason Wang wrote: > > On 2020/4/2 ??12:08, Michael S. Tsirkin wrote: > > On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > > > >From 9b3a5d23b8bf6b0a11e65e688335d782f8e6aa5c Mon Sep 17 00:00:00 2001 > > > From: Jason Wang <jasowang at redhat.com> > > > Date: Wed, 1 Apr 2020 22:17:27 +0800 >