From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id qGXHOVwID2VVDQAAG6o9tA:P1 (envelope-from ) for ; Sat, 23 Sep 2023 17:46:37 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id qGXHOVwID2VVDQAAG6o9tA (envelope-from ) for ; Sat, 23 Sep 2023 17:46:37 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id A61BE45F76 for ; Sat, 23 Sep 2023 17:46:36 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=khxqWe00; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1695483996; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=X39jAVvNxsjelGSa4cUpcAR2tnaBDlXY/1dia/ootgM=; b=MMYSyAah71wgA6MSExJ9WjEy2Eb9288/QjJQwtXeoC6dFPPvVjX9uESYeQk4ENpzBwb/QU lgqMQKW+sgt8ydLmtjUWx8Fi2W4oBOmcCnIwyfS/y1eBL5eAUQMRfI4uur83NAhpUffsHQ K3p7a2j2kVGxdWzSk4yz2jGHwMfl7t/GnwrtdKYG+wIvN1z51xq8JvlZx9etGxydGt+20M aPleEzWUhVzjGoJPg8X2QdsuOiUkdhoXGdVP6eBTPpfW7k4mrbAZHXgpVQqxzHbvQvd7jR jKNSam32g8054b6bo7IRMBzjBdFLaBhoLXsyrWQNN+QpibD3uZUjm4wIaCj9bQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1695483996; a=rsa-sha256; cv=none; b=cfrW4Whp0n1rnvmkvBDxmlPasQZ9ysqjnD86Iv7aorQ2dKOZgvEb1RiKBVOf2eB1P6uEIK xH8Wr7203ISqzr+E0UW2zkO1zSZTMpQcSjCzc3mwzj8jMpR1k3tBSLU7/abHbQT9x4NhOJ pirUCagb3FO6vK3AeExTsQYxff3CXeVkQPHp+jtIktJng+GwbX2bjQKSShivjglDtxIZoU sh7T3ek3JQfTAAWc4zBBrtAwo5ecAosd5bhqwe3jXivXVBGnuznY7cbn1rXrsZ47FnxcpT dX45kV6aze8U5XZBHMjC4oWNABeWX4EIsm3TWJBFvJSXgzsqVUdxyxAminC5Ow== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=khxqWe00; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qk4pB-0007w1-At; Sat, 23 Sep 2023 11:45:41 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qk4p8-0007uE-QE for emacs-orgmode@gnu.org; Sat, 23 Sep 2023 11:45:38 -0400 Received: from mail-qt1-x844.google.com ([2607:f8b0:4864:20::844]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qk4p7-0004xv-8Y for emacs-orgmode@gnu.org; Sat, 23 Sep 2023 11:45:38 -0400 Received: by mail-qt1-x844.google.com with SMTP id d75a77b69052e-417fa15f1f9so4804811cf.1 for ; Sat, 23 Sep 2023 08:45:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695483936; x=1696088736; darn=gnu.org; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:to:from:from:to:cc:subject:date:message-id:reply-to; bh=X39jAVvNxsjelGSa4cUpcAR2tnaBDlXY/1dia/ootgM=; b=khxqWe003ASFhIr5JFTl0soyRbR/u8m2WOnZ6Dy/HccdzAbopR0GCrKoHODl4fC5DG Ec7jkT0hXG4LSo8xnpwRm4avnzkrNpBgIp942vvkLLQZHb49jyKC0NsCPR2BCd0/rCIy RVaoZmsvzgbv0ZgcqlbU+Fe7PDqQF93TLvWT0E+4hY5slLf/upOh9Lsv/5fGiBH1VWkA UihYqPSkCp4VMeVPDDcRN7jaXNp/dY4pH25bu5JqaL40d8dbY7HJEwUoKU9ObaamR18L 7rQyr3r6f+JcYk/Bl5guZssZ1FEMdPM0oM/Idui8IOdqrjM4hQS8OF+Zahksze888ZNR tcxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695483936; x=1696088736; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=X39jAVvNxsjelGSa4cUpcAR2tnaBDlXY/1dia/ootgM=; b=UPxuNzuYIdmpQU2pmHTHWeLmjIepL/RUbt0M+qtdb2wOZSPcqNI9F65ZPJrEMvkhD/ A0myv9+LEEQswkRO3cYUGnkt0WrQoVgAMqyv8wsbvlIyvZcKoW2kdrlssYCDQWFhGzW/ uHW8avZ/fxVTwCwSzJr2Sb5K9vxiHmAPrBa5v13xW+02Adtrx4YCEMsiV/WiJqcsXwjy dK648FAuYqbOJvrAhxFimn/eHHsbCz27elTD46Awu+PZcb2D0RMqnHMRU6PsO6gQQyS0 F37TK9xYjdIiymCq+rtSuciK9tkbnxOG7UruBo1dvliCpyjiFTH/7r8fJGoPNyz08Wo2 A2UA== X-Gm-Message-State: AOJu0Yy6+DZLaXC52sp0pnHF5hNZMH1y+6g6/N024wEfhN9+x2k1JIlr nBuk8wNBmyFeKhuCuoSaocgMNBgEbOPaJg== X-Google-Smtp-Source: AGHT+IH4sSRozxnC0/iz9gno/76ympOEbAMSq2E7L9LZ5RLGkMz50Bwwh72VVFpRo+yt3XYUj25XJA== X-Received: by 2002:a05:622a:296:b0:416:ea40:6e84 with SMTP id z22-20020a05622a029600b00416ea406e84mr2641437qtw.2.1695483935951; Sat, 23 Sep 2023 08:45:35 -0700 (PDT) Received: from fig.gmail.com ([146.70.198.175]) by smtp.gmail.com with ESMTPSA id g13-20020ac8070d000000b0040f8ac751a5sm2351721qth.96.2023.09.23.08.45.35 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 23 Sep 2023 08:45:35 -0700 (PDT) From: Suhail Singh To: emacs-orgmode@gnu.org Subject: Re: [FR] Make notion of "modification time" configurable during publishing In-Reply-To: (Ihor Radchenko's message of "Sat, 23 Sep 2023 12:35:49 +0200") References: Date: Sat, 23 Sep 2023 11:45:35 -0400 Message-ID: <87msxcj3kw.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::844; envelope-from=suhailsingh247@gmail.com; helo=mail-qt1-x844.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Spam-Score: -6.68 X-Migadu-Spam-Score: -6.68 X-Migadu-Scanner: mx1.migadu.com X-Migadu-Queue-Id: A61BE45F76 X-TUID: 40461OAWOnqg Ihor Radchenko writes: > But do you actually use one but not other in practice? As in, could users have a preference for one vs the other in practice? Yes, since the choice isn't without consequence, it's conceivable (generally speaking) that some would prefer one over the other. FWIW, in my specific case, I use CommitDate, but I am not convinced it's "the right thing" in all situations. Not having conducted a survey, I also cannot comment on the frequency with which users have a desired preference for one vs the other. I am also not aware of general rules where users would necessarily prefer one over the other, but it's possible they may exist. My point was to simply point out that there is more than one interpretation of "vc-modification-time". > It should not be too hard to add buffer hash calculation there. No disagreement there. > It will only work for files without includes and force us to use > exactly the same hash algorithm. I don't follow. I was stating that the concept of a "file hash" could be obtained in more than way. I.e., in addition to it being calculated "by hand" it would also be possible to query an oracle (the VCS in this case) for it. This is distinct and orthogonal from the decision of how a "file with includes" is handled. If I understand you correctly, the logic you have in mind, would be something like this: - during publish, compare the file hash of the file being published as well as all included files - if the values for all are the same as in the cache, don't publish (if user has signalled such intent via the equivalent of org-publish-use-timestamps-flag) - if the value of any one is different, re-publish and update cache with the updated file hashes It doesn't matter how the specific file hash is obtained, as long as the mechanism is being used consistently and the file hash of the included files are also being consulted in an appropriate way. -- Suhail