mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Johannes Schindelin <>
Cc: Johannes Schindelin via GitGitGadget <>,
Subject: Re: [PATCH 0/2] stash: handle pathspec magic again
Date: Mon, 18 Mar 2019 16:02:44 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Junio C. Hamano's message of "Mon, 18 Mar 2019 13:39:34 +0900")

Junio C Hamano <> writes:

> Johannes Schindelin <> writes:
>> Fine. But in that case, I would appreciate not being reminded of the
>> messiness. Not unless you let me do something about it. Don't put me
>> between a rock and a hard place, please.

Perhaps your attitude is coming from a fundamental misunderstanding
of the process.  Don't be unnecessarily defensive, as nobody is
being hostile or attacking you.

It's not like this is a competition to see if your taste as a
developer is better or worse than others (including me).  It is a
cooperative process and everybody involved is "at fault" if we made
a mistake.  Ending up with a suboptimal history in 'next' is not
creditable solely to you.  I am as much to blame, so are others who
advocated to merge it to 'next' even it were not ready.  Or those
who did not speak up before it was too late, for that matter.

> Gagging me won't change the fact that the history we ended up is
> messy.  Without getting reminded of our past mistake(s) ourselves,
> what else encourages us to do better the next time?

      reply	other threads:[~2019-03-18  7:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 15:29 [PATCH 0/2] stash: handle pathspec magic again Johannes Schindelin via GitGitGadget
2019-03-07 15:29 ` [PATCH 1/2] legacy stash: fix "rudimentary backport of -q" Johannes Schindelin via GitGitGadget
2019-03-11  7:27   ` Junio C Hamano
2019-03-07 15:29 ` [PATCH 2/2] built-in stash: handle :(glob) pathspecs again Johannes Schindelin via GitGitGadget
2019-03-11  7:28   ` Junio C Hamano
2019-03-11 16:27     ` Johannes Schindelin
2019-03-11 22:19       ` Thomas Gummerer
2019-03-08  1:37 ` [PATCH 0/2] stash: handle pathspec magic again Junio C Hamano
2019-03-08 16:12   ` Johannes Schindelin
2019-03-10  0:56     ` Junio C Hamano
2019-03-11 16:25       ` Johannes Schindelin
2019-03-18  4:39         ` Junio C Hamano
2019-03-18  7:02           ` Junio C Hamano [this message]

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:

  List information:

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

  git send-email \ \ \ \ \ \

* 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

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).