git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)
Date: Thu, 17 Jun 2021 23:28:18 -0500	[thread overview]
Message-ID: <60cc20e2361fa_5d7b8208fe@natae.notmuch> (raw)
In-Reply-To: <YMvofq5aSryQzpZQ@coredump.intra.peff.net>

Jeff King wrote:
> On Thu, Jun 17, 2021 at 11:58:25PM +0000, brian m. carlson wrote:
> 
> > On 2021-06-17 at 02:55:26, Junio C Hamano wrote:
> > > * bc/doc-asciidoctor-to-man-wo-xmlto (2021-05-14) 2 commits
> > >  - doc: remove GNU_ROFF option
> > >  - doc: add an option to have Asciidoctor build man pages directly
> > > 
> > >  An option to render the manual pages via AsciiDoctor bypassing
> > >  xmlto has been introduced.
> > > 
> > >  What is the status of this one?
> > 
> > Probably best to drop it.  I think Felipe didn't want his sign-off on
> > it, and I don't think there's a good way to produce an equivalent patch
> > without incorporating his changes.  We don't seem to see eye to eye on
> > an appropriate solution to the problem, and I don't feel like arguing
> > about it further.
> 
> Hmm. I'm not sure if that's a good resolution here. I do think many
> people were positive in moving in that direction.

I don't know what you mean by "that direction", but I was the one that
included your patches on top of his series [1], not brian.

So, if your patches have anything to do with "that directioon", you are
on my side.

Cheers.

[1] https://lore.kernel.org/git/20210521224452.530852-1-felipe.contreras@gmail.com/

-- 
Felipe Contreras

  reply	other threads:[~2021-06-18  4:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  2:55 What's cooking in git.git (Jun 2021, #06; Thu, 17) Junio C Hamano
2021-06-17  9:38 ` jh/builtin-fsmonitor, was " Johannes Schindelin
2021-06-17  9:40 ` js/subtree-on-windows-fix, " Johannes Schindelin
2021-06-17 12:38 ` Contributions which I feel are dangerous and/or deceptive (Was: Re: What's cooking in git.git (Jun 2021, #06; Thu, 17)) Elijah Newren
2021-06-17 14:19   ` Felipe Contreras
2021-06-17 15:06     ` Elijah Newren
2021-06-17 16:58       ` Felipe Contreras
2021-06-17 14:42 ` What's cooking in git.git (Jun 2021, #06; Thu, 17) Felipe Contreras
2021-06-17 23:58 ` brian m. carlson
2021-06-18  0:27   ` Jeff King
2021-06-18  4:28     ` Felipe Contreras [this message]
2021-06-19  7:18     ` Junio C Hamano
2021-06-19 17:27       ` Ignoring valid work Felipe Contreras
2021-06-18  4:20   ` What's cooking in git.git (Jun 2021, #06; Thu, 17) Felipe Contreras
2021-06-18 16:32 ` Jeff Hostetler
2021-06-25 22:21 ` Emily Shaffer
2021-06-25 22:26   ` Randall S. Becker
2021-06-28 16:46   ` Jeff Hostetler

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=60cc20e2361fa_5d7b8208fe@natae.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=sandals@crustytoothpaste.net \
    /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).