unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>, rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: master e714b31 3/6: Merge from origin/emacs-28
Date: Wed, 10 Nov 2021 12:09:44 -0800	[thread overview]
Message-ID: <CADwFkmmkqperpao7EoGzPH4t4-fk_f3NcO7Gpw78kNx-TMkrrg@mail.gmail.com> (raw)
In-Reply-To: <838rxv3iqs.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Look closer, please.

It is up to you to produce evidence for your claims, or they will remain
unsubstantiated.

You claimed in the past that we can solve this and make everyone happy:

    https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20403#33

Nothing has changed since then, besides your newly discovered opposition
to these changes.

>> The existence of the special code for this in gitmerge is already proof
>> that this is suboptimal.  If it is buggy, that makes it worse of course.
>
> Nonsense.  It just means we haven't yet got the full solution for
> that.

The better choice is to just not to create problems for ourselves in the
first place.

>> But even if there are no bugs in gitmerge.el, today or in the future, we
>> still lose the ability to use "git blame" in etc/NEWS.NN for the
>> previous release on master.
>
> "git annotate" on NEWS is pretty meaningless anyway.  Stuff gets moved
> there too much for that to be useful.

Some posters on this mailing list *do* use it (me included):

    "I use VC archeology on NEWS all the time.  It is handy when I need to
    know who and when added some new feature."

    https://lists.gnu.org/archive/html/emacs-devel/2021-09/msg00534.html

>> And what's the upside?  None, AFAICT.
>
> You are biased, so you only see the side that suits you.

That is just a run-of-the-mill ad-hominem.  If you disagree, feel free
to present substantial arguments instead.  I see no serious arguments so
far, yet you claim to be the one that is "unbiased".

> The upside is that we are using this for a long time, and any problems
> we see now are minor.

We have also had issues with it for a long time.  I have already
provided the evidence to back that claim up, but here's some more:

    "At present, emacs26:etc/NEWS has to get merged to master:etc/NEWS.26.
    This is a PITA at every single merge.

    "If the file was already called NEWS.26 on both branches,
    all these merge problems would go away."

    https://debbugs.gnu.org/cgi/bugreport.cgi?bug=20403#30



  parent reply	other threads:[~2021-11-10 20:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211106092430.31690.17236@vcs0.savannah.gnu.org>
     [not found] ` <20211106092433.20A2420A22@vcs0.savannah.gnu.org>
2021-11-10 15:55   ` master e714b31 3/6: Merge from origin/emacs-28 Robert Pluim
2021-11-10 16:41     ` Stefan Monnier
2021-11-10 17:12     ` Eli Zaretskii
2021-11-10 17:18       ` Robert Pluim
2021-11-10 18:24         ` Juri Linkov
2021-11-10 18:37           ` Juri Linkov
2021-11-10 18:53             ` Eli Zaretskii
2021-11-10 19:06               ` Juri Linkov
2021-11-10 19:13                 ` Eli Zaretskii
2021-11-10 18:46         ` Eli Zaretskii
2021-11-10 17:49       ` Stefan Kangas
2021-11-10 18:47         ` Eli Zaretskii
2021-11-10 19:19           ` Stefan Kangas
2021-11-10 19:36             ` Eli Zaretskii
2021-11-10 19:50               ` Dmitry Gutov
2021-11-10 20:09               ` Stefan Kangas [this message]
2021-11-11  7:23             ` Michael Albinus
2021-11-10 19:37           ` Stefan Kangas
2021-11-11  1:24     ` Lars Ingebrigtsen
2021-11-17  4:04       ` Stefan Kangas
2021-11-17  7:11         ` Eli Zaretskii
2021-11-17  7:56           ` Lars Ingebrigtsen
2021-11-17  9:58             ` Eli Zaretskii
2021-11-17 14:03             ` Eli Zaretskii
2021-11-18  1:59               ` Stefan Kangas
2021-11-18  8:07                 ` Eli Zaretskii
2021-11-18  9:25                   ` Lars Ingebrigtsen
2021-11-18 11:10                     ` Eli Zaretskii
2021-11-18 16:27                       ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmmkqperpao7EoGzPH4t4-fk_f3NcO7Gpw78kNx-TMkrrg@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.org \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).