From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Vladimir Kazanov Newsgroups: gmane.emacs.devel Subject: Re: The overlay branch (yet again) Date: Fri, 6 Dec 2019 06:48:02 +0000 Message-ID: References: <83blsmiz3l.fsf@gnu.org> <8336dyiv7q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="262784"; mail-complaints-to="usenet@blaine.gmane.org" Cc: martin rudalics , Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 06 18:32:06 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1idHSX-0016EW-PP for ged-emacs-devel@m.gmane.org; Fri, 06 Dec 2019 18:32:05 +0100 Original-Received: from localhost ([::1]:42030 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1idHSV-0005pp-BR for ged-emacs-devel@m.gmane.org; Fri, 06 Dec 2019 12:32:03 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51823) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1idFlA-0005tc-3v for emacs-devel@gnu.org; Fri, 06 Dec 2019 10:43:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1idFl8-0000U3-RV for emacs-devel@gnu.org; Fri, 06 Dec 2019 10:43:11 -0500 Original-Received: from mail-oi1-x241.google.com ([2607:f8b0:4864:20::241]:39803) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1idFl6-0000PI-Vg; Fri, 06 Dec 2019 10:43:09 -0500 Original-Received: by mail-oi1-x241.google.com with SMTP id a67so133813oib.6; Fri, 06 Dec 2019 07:43:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=gC2rxWzem68xiaK5dO3QveASiVdvh7WU23t0GV3XAvw=; b=pR+e7ftrsKg7FwOqvJVg771r1U/ZkfZ3un9aezJJqjRko8aqF/r0Gb89d/V7BxUQOV rMn/qLLOFAx/hvPlfLvFRdVusCamCEnRW+0Spnc68iLHp5ccvLmhnfby4ScenacT34sz aAHxQwmfu+owvi4J5sOzo8By6DSGU0n9peo5RbjHAWskuIs9xOV19xkbaImMxaVRaYfA 1jCTbKMLLKGiPyN5EJgVpzRtSXleW/PvGr0gSHHdlSp5pA1x7YfqCc6z50gQVqNBZwhM Z90uiDwC+4X9Oq3FOyqx2hksQTX72WZIpj91zlTYLWMuBqXnLfLEUWFi9KY0wDJwyCO9 i61g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=gC2rxWzem68xiaK5dO3QveASiVdvh7WU23t0GV3XAvw=; b=VFZ/gbiXGJtGbyPEZfuUdY6/yY0+Isz/e5wbRRkZSHRJsHQETxAXICXQr+Q3U7QOrU lFEsbXU4fUWAta7SKjwC15RYYNRtuBGmZkmQtpSiCUBSF4dwuBv2+YxYiA6Fd+yMChMu H9ZX1GBWwc0cAJtNY9zeSPE0Kpa5yVVO054L10PU9bDRj1POxR/MbFN5CatMiarQcGnl QjfSijxZTbTzqjgQ3zJzJoeCvngSNd/MbhESw+qKnEEaQqVYgMZTzQjGtFISH5wjDq0T B9J2Y16SKYR0HaYLusYo5MEh8mxlu7WWMOlqfT0CNXla5IFR+2SS1QUnqBn5S7Z4lXyb bCCg== X-Gm-Message-State: APjAAAXGoSfCsDJnVn4mpHfmajHkTECcqU1u6B71zImT916sHHdDysmr XEf7LVL+l1rGjU5UdQ/c+2XE2NDFvzuTwRoh/YTT X-Google-Smtp-Source: APXvYqygdbVbFwJ9/l9K70Z+CVcdikhry9x9ULFsKTFjd1JYiXZmpDJO6RHjGaQkApC+h5IHo1+NojhMhK3tVEbERyA= X-Received: by 2002:aca:4850:: with SMTP id v77mr8767785oia.70.1575614896184; Thu, 05 Dec 2019 22:48:16 -0800 (PST) In-Reply-To: <8336dyiv7q.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::241 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243183 Archived-At: On Thu, Dec 5, 2019 at 4:38 PM Eli Zaretskii wrote: > It would, but how would you produce such a patch if there's a single > commit on the branch, which mixes these changes with others? I wouldn't, at least not this time. But I already have a second patch in the works, and I really want it to be usable the way I send it.. Stefan already merged the patch, by the way. Nice! -- Yours sincerely, Vladimir Kazanov -- =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC, =D0=92=D0=BB=D0=B0=D0=B4=D0=B8=D0=BC=D0=B8=D1=80 =D0=9A=D0=B0=D0=B7=D0=B0= =D0=BD=D0=BE=D0=B2