public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
	Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
	Thomas Schwinge <tschwinge@baylibre.com>,
	Sam James <sam@gentoo.org>, Mark Wielaard <mark@klomp.org>,
	"binutils@sourceware.org" <binutils@sourceware.org>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	David Malcolm <dmalcolm@redhat.com>,
	"arsen@gentoo.org" <arsen@gentoo.org>,
	Alexandre Oliva <aoliva@gcc.gnu.org>
Subject: Re: Help needed with maintainer-mode
Date: Tue, 5 Mar 2024 14:26:40 +0000	[thread overview]
Message-ID: <dc1eb309-5e6e-4ee2-9637-8bfce325ccf8@arm.com> (raw)
In-Reply-To: <CAH6eHdTwEenLVNyG=Wo=9pt6DYZxvzRJ53s6H50VDfHj+BhUsQ@mail.gmail.com>

On 04/03/2024 20:04, Jonathan Wakely wrote:
> On Mon, 4 Mar 2024 at 19:27, Vladimir Mezentsev
> <vladimir.mezentsev@oracle.com> wrote:
>>
>>
>>
>> On 3/4/24 09:38, Richard Earnshaw (lists) wrote:
>>> Tools like git (and svn before it) don't try to maintain time-stamps on patches, the tool just modifies the file and the timestamp comes from the time of the modification.  That's fine if there is nothing regenerated within the repository (it's pure original source), but will cause problems if there are generated files as their time stamps aren't necessarily correct.  `gcc_update --touch` addresses that by ensuring all the generated files are retouched when needed.
>>
>> Why do we save generated files in the source tree?
>> What will be the problem if we remove Makefile.in and configure from
>> source tree and will run `autoreconf -i -f` before building ?
> 
> Having the exact correct versions of autoconf and automake increases
> the barrier for new contributors to start work. And to regenerate
> everything, they also need autogen, mkinfo, etc.

It's worse than that.  They might need multiple versions of those tools because different subtrees are built with different, subtly incompatible, versions of those tools.

R.


  reply	other threads:[~2024-03-05 14:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 10:22 Christophe Lyon
2024-02-29 10:41 ` Richard Earnshaw (lists)
2024-02-29 17:36   ` Christophe Lyon
2024-02-29 11:00 ` Mark Wielaard
2024-02-29 17:39   ` Christophe Lyon
2024-03-01 13:08     ` Mark Wielaard
2024-03-01 13:21       ` Christophe Lyon
2024-03-01 16:32       ` Christophe Lyon
2024-03-03 21:15         ` Mark Wielaard
2024-03-04  0:30           ` Sam James
2024-03-04  9:36             ` Thomas Schwinge
2024-03-04 10:42               ` Christophe Lyon
2024-03-04 11:25                 ` Jonathan Wakely
2024-03-04 14:46                   ` Christophe Lyon
2024-03-04 15:36                     ` Richard Earnshaw (lists)
2024-03-04 15:40                       ` Richard Earnshaw
2024-03-04 16:42                         ` Christophe Lyon
2024-03-04 17:38                           ` Richard Earnshaw (lists)
2024-03-04 19:27                             ` Vladimir Mezentsev
2024-03-04 20:04                               ` Jonathan Wakely
2024-03-05 14:26                                 ` Richard Earnshaw (lists) [this message]
2024-03-05 15:39                                   ` Richard Earnshaw
2024-03-06 15:04     ` Andrew Carlotti
2024-03-06 17:22       ` Richard Earnshaw (lists)
2024-02-29 19:49 ` Thiago Jung Bauermann
2024-03-01 10:09   ` Christophe Lyon

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=dc1eb309-5e6e-4ee2-9637-8bfce325ccf8@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=aoliva@gcc.gnu.org \
    --cc=arsen@gentoo.org \
    --cc=binutils@sourceware.org \
    --cc=christophe.lyon@linaro.org \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jwakely.gcc@gmail.com \
    --cc=mark@klomp.org \
    --cc=sam@gentoo.org \
    --cc=tschwinge@baylibre.com \
    --cc=vladimir.mezentsev@oracle.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 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).