All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
	The development of GNU GRUB <grub-devel@gnu.org>,
	Daniel Axtens <dja@axtens.net>,
	Robbie Harwood <rharwood@redhat.com>
Subject: Re: [PATCH] Retire ChangeLog-2015
Date: Fri, 25 Feb 2022 12:04:56 -0500	[thread overview]
Message-ID: <20220225170455.m2t44rrc3vswkvp5@redhat.com> (raw)
In-Reply-To: <20220225120348.zofuoe4njt4wfrgo@tomti.i.net-space.pl>

On Fri, Feb 25, 2022 at 01:03:48PM +0100, Daniel Kiper wrote:
> On Fri, Feb 25, 2022 at 11:33:09AM +0100, Javier Martinez Canillas wrote:
> > Hello Peter,
> >
> > Thanks a lot for your patch.
> >
> > On 2/24/22 22:55, Peter Jones wrote:
> > > ChangeLog-2015 has been untouched for over 7 years now, and any
> > > information in it is purely for historical purposes.  At the same time,
> > > grepping for code winds up matching this file quite a bit, almost never
> > > accomplishing anything other than cluttering up your grep results.  We
> > > don't need this in the main repo, and "git show" will find it if you're
> > > looking at the old history of commits on some file.
> > >
> > > This patch deletes it.
> >
> > Yes, let's *please* get rid of this ChangeLog. It doesn't add any
> > value AFAICT and makes doing greps over the codebase much harder.
> >
> > > Signed-off-by: Peter Jones <pjones@redhat.com>
> > > Reviewed-by: Daniel Axtens <dja@axtens.net>
> > > Reviewed-by: Robbie Harwood <rharwood@redhat.com>
> >
> > Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> 
> I agree with above but it requires more than just ChangeLog-2015 file
> removal. The file is referenced at least in Makefile.am.

I've sent a follow-up that fixes this as well.

> Additionally, may we consider addition of a script which generates
> ChangeLog file from the git log? I think we could steal it from here
> [1][2].

Feel free, but IMO that's unrelated to this patch, which just cleans up
old goo in the repo.

> And if we do that I think we could drop NEWS file too (it is
> referenced in README; so, it should be dropped from there too).

Again, fine with me, but unrelated to this. ChangeLog-2015 is /in
everyone's way/.

-- 
        Peter



  parent reply	other threads:[~2022-02-25 17:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 21:50 [PATCH] Retire ChangeLog-2015 Peter Jones
2022-02-24 21:55 ` Peter Jones
2022-02-25 10:33   ` Javier Martinez Canillas
2022-02-25 12:03     ` Daniel Kiper
2022-02-25 16:27       ` Javier Martinez Canillas
2022-02-25 16:28       ` Peter Jones
2022-03-01 15:25         ` Daniel Kiper
2022-02-25 17:04       ` Peter Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-20 16:51 Peter Jones
2020-11-21 14:24 ` Daniel Axtens
2021-10-26 19:42   ` Robbie Harwood

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

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

  git send-email \
    --in-reply-to=20220225170455.m2t44rrc3vswkvp5@redhat.com \
    --to=pjones@redhat.com \
    --cc=daniel.kiper@oracle.com \
    --cc=dja@axtens.net \
    --cc=grub-devel@gnu.org \
    --cc=javierm@redhat.com \
    --cc=rharwood@redhat.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.