From: "James Bottomley" <James.Bottomley@HansenPartnership.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
toke@toke.dk,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
users@linux.kernel.org, tools@linux.kernel.org,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [kernel.org users] b4: encouraging using the cover letter in merge commits?
Date: Sat, 19 Dec 2020 15:34:24 -0800 [thread overview]
Message-ID: <1fdc0edd747d58cd1a09c1d5fd0f0a22b83d4f45.camel@HansenPartnership.com> (raw)
In-Reply-To: <20201219221730.GD363602@kernel.org>
On Sat, 2020-12-19 at 19:17 -0300, Arnaldo Carvalho de Melo wrote:
> Em Sat, Dec 19, 2020 at 01:57:06PM -0800, James Bottomley escreveu:
> > On Sat, 2020-12-19 at 18:43 -0300, Arnaldo Carvalho de Melo wrote:
> > > But we are digressing, assuming what is in the cover letter is
> > > not what should be in individual commits but has value, why not
> > > have it preserved upstream?
>
> > Because on its own it's incomplete and we have other mechanisms to
> > keep the full historical record.
>
> I agree that link tags points to the relevant discussion, and I hope
> that where that is preserved is available as long as the main repo is
> available, but that is only a hope, as it is disjoint from the main
> repository, keeping such valuable information in the main repository
> is still important IMHO.
OK, so I think we see the email archives in different ways. I see them
as a thing, like the repo, which will always be there. Even if
kernel.org gets sold off by the LF and we lose lore, there are a bunch
of internet heritage and archive projects making sure our history will
be preserved. The link tag, since it's based on the msgid, will always
be usable through them.
I think you see this as less certain, hence the need to save the cover
letter, so in essence this comes down to *who* should preserve the
information.
> Its not like having cover letters in the main repository will cause
> major disruption or excessive overhead.
I'm not saying no-one should do it, I'm saying preserving cover letters
in merge commits is incompatible with the current linear workflow and
that link tags with that workflow provides a superset of the
information in the cover letter so there's no reason for anyone using
the linear workflow to move to a merge commit workflow.
James
next prev parent reply other threads:[~2020-12-19 23:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 21:32 b4: encouraging using the cover letter in merge commits? Toke Høiland-Jørgensen
2020-12-18 22:09 ` Konstantin Ryabitsev
2020-12-19 12:29 ` Toke Høiland-Jørgensen
2020-12-18 22:38 ` [kernel.org users] " James Bottomley
2020-12-19 12:34 ` Toke Høiland-Jørgensen
2020-12-19 17:03 ` James Bottomley
2020-12-19 17:21 ` Jakub Kicinski
2020-12-19 17:32 ` James Bottomley
2020-12-21 19:05 ` Jason Gunthorpe
2020-12-21 21:13 ` Michal Kubeček
2020-12-21 21:30 ` Arnaldo Carvalho de Melo
2020-12-22 6:30 ` Leon Romanovsky
2020-12-22 8:14 ` Geert Uytterhoeven
2020-12-22 12:36 ` Leon Romanovsky
2021-01-05 13:38 ` Jason Gunthorpe
2020-12-19 18:45 ` Jonathan Corbet
2020-12-19 18:49 ` James Bottomley
2020-12-19 18:57 ` Jonathan Corbet
2020-12-19 19:03 ` James Bottomley
2020-12-19 20:48 ` Arnaldo Carvalho de Melo
2020-12-19 21:01 ` James Bottomley
2020-12-19 21:43 ` Arnaldo Carvalho de Melo
2020-12-19 21:57 ` James Bottomley
2020-12-19 22:17 ` Arnaldo Carvalho de Melo
2020-12-19 23:34 ` James Bottomley [this message]
2020-12-21 17:34 ` [tools] " Mark Brown
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=1fdc0edd747d58cd1a09c1d5fd0f0a22b83d4f45.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=acme@kernel.org \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=toke@toke.dk \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.org \
/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 NNTP newsgroup(s).