From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: Organizing the NEWS file a bit better Date: Mon, 6 Sep 2021 20:57:43 +0200 Message-ID: References: <87wnnwp3g8.fsf@gnus.org> <87tuiyqklv.fsf@mail.linkov.net> <87sfyije12.fsf@gnus.org> <87ilzejcrr.fsf@gnus.org> <83h7exr1fn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20197"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , Emacs developers , Juri Linkov To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Sep 06 20:58:49 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mNJpQ-00053D-Jt for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Sep 2021 20:58:48 +0200 Original-Received: from localhost ([::1]:49366 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mNJpP-0001uT-21 for ged-emacs-devel@m.gmane-mx.org; Mon, 06 Sep 2021 14:58:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40664) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mNJob-0001FY-Lf for emacs-devel@gnu.org; Mon, 06 Sep 2021 14:57:57 -0400 Original-Received: from mail-pj1-f54.google.com ([209.85.216.54]:41822) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mNJoa-0004ct-At; Mon, 06 Sep 2021 14:57:57 -0400 Original-Received: by mail-pj1-f54.google.com with SMTP id m21-20020a17090a859500b00197688449c4so80423pjn.0; Mon, 06 Sep 2021 11:57:55 -0700 (PDT) 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; bh=K3Pm16F2r5GjCZiMQovwvaKb+8uTOMPOb1z3sAOoiAU=; b=QJok/qiBv40Qp4hANYvE2o1joyHcA/ogYfxZVmXeJxcBu72hVwcqkYc8lDs3vLXqnR BCBW+d92/vESQfFE/TBbvsa48quitdj1Y0lpEDaBYG5cAUTfpl6zToSfyYtyCKbDDFod efLD08YPkEz41N2Zgah2zVLlLbCeNJr8Ufy2SzpyPGc7oZC0FC3IgzZY0KXRXh7Kc9Zc r/608uxZ3x0gWwxy0416vooNjyCiM6+XFOzIdkDNx9Iwzi3jhH7689DkK6mxzeqQXBNZ g28v0QoepJHBkt48ubv7XHpoa+K0b41w39vfatH/pVRtACgksGGfugBKR/+5iQWMX3aP bzpg== X-Gm-Message-State: AOAM533xyfxqaTBpuOd1cqenRtDeT5f7wbl62N9czibnhgXhbg+G6c0z MIv6TRlqSgDBD1tXbda1nG3TrmyUvoKPG61HG7WccmHN X-Google-Smtp-Source: ABdhPJw7evva66qA51AThrVubtrhamIAZeAmOzsLQV1yzkWne/IAuISY5uMWSbHF1WFqEeWlfBgVXv9R4eI1FDl9W7s= X-Received: by 2002:a17:902:b691:b029:12d:2b6:d116 with SMTP id c17-20020a170902b691b029012d02b6d116mr11765051pls.71.1630954674546; Mon, 06 Sep 2021 11:57:54 -0700 (PDT) In-Reply-To: <83h7exr1fn.fsf@gnu.org> Received-SPF: pass client-ip=209.85.216.54; envelope-from=stefankangas@gmail.com; helo=mail-pj1-f54.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:274167 Archived-At: Eli Zaretskii writes: > > AFAICT, VC archeology is already not very convenient after we cut the > > release branch and move the file from etc/NEWS to etc/NEWS.28. One > > would need to visit the relevant release branch first. > > I use VC archeology on NEWS all the time. It is handy when I need to > know who and when added some new feature. In NEWS, I'm pretty sure that most of us do. Lars' point was that it's nice that file history is preserved when the markers are removed. But those markers are only removed on the release branch, in preparation of a release. On master, the file is moved to make way for a new NEWS file. This breaks archeology anyways. (I hope we could improve this process so we don't have to move the file. This has been discussed elsewhere.) > > (As a Magit user, walking backwards in "git blame" history for one > > line that hasn't moved is just a matter of typing "b" one or more > > times. I have no idea how easy this is using vc, but I've assumed > > it's harder since people are concerned about it.) > > Wrong tool, I think. Try vc-region-history (I'm sure Magit has > something similar). The relevant Git command is "git log -L". I've never used vc-region-history, but it is pretty neat. If I understand correctly, it breaks when lines are moved? I think the better tool to use for archeology in NEWS, where lines are frequently moved, is vc-annotate. Using it, I can now see that it allows me to trace changes backward in time (but it does involve more typing and more new buffers than in Magit, and I remember now that this is why I stopped using it).