tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnaldo Carvalho de Melo" <acme@kernel.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
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 17:48:32 -0300	[thread overview]
Message-ID: <20201219204832.GA363602@kernel.org> (raw)
In-Reply-To: <12042294a3996c27d4f595f26bc1f54c1a4543a2.camel@HansenPartnership.com>

Em Sat, Dec 19, 2020 at 11:03:59AM -0800, James Bottomley escreveu:
> On Sat, 2020-12-19 at 11:57 -0700, Jonathan Corbet wrote:
> > On Sat, 19 Dec 2020 10:49:21 -0800
> > "James Bottomley" <James.Bottomley@HansenPartnership.com> wrote:
> > 
> > > However, the link tag does preserve the cover letter and all the
> > > series information, why do you think it doesn't?
> > 
> > The information is essentially there, though one step further removed
> > from the repository.  But it documents the series as posted, not as
> > applied; one expects the two to be the same most of the time, but
> > that's not always the case.
> 
> But if it's not the case the change is supposed to be documented in the
> commit in square brackets.  I suppose the one interesting case is when
> a commit gets dropped from a series, but that should be somewhere in
> the link tag email trail.
> 
> > We're getting into minor details, though.  If The Community were to
> > decide somehow that link tags are The Preferred Way, I would not kick
> > and scream too hard before going along with it.  Unless I were in one
> > of my screaming moods at the time, of course.
> 
> I'm not really seeking a preferred way, I'm just asking why people who
> now use the link tag and linear series should change.  As long as we
> can agree the link tag is fine and there's really no additional
> information that needs capturing, I think we can leave it to maintainer
> discretion whether they prefer merge per series or linear.

My question is: is the information in the cover letter useful? If it is,
why not have it preserved in the main repo? The owner of such
repositories asks us to describe what is in the series, sign it, and
then this gets dropped?

- Arnaldo

  reply	other threads:[~2020-12-19 20:48 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 [this message]
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
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=20201219204832.GA363602@kernel.org \
    --to=acme@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --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).