All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smith <ischis2@cox.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
	Emily Shaffer <emilyshaffer@google.com>,
	peff@peff.net
Subject: Re: Should we auto-close PRs on git/git?
Date: Tue, 12 Nov 2019 22:29:45 -0700	[thread overview]
Message-ID: <11925817.qcmArAFNWq@thunderbird> (raw)
In-Reply-To: <xmqqtv7dlkcb.fsf@gitster-ct.c.googlers.com>

On Friday, November 8, 2019 9:55:32 PM MST Junio C Hamano wrote:
> > But to me, this seems like a sort of Sisyphean task ...
> 
> Yeah, I would not stop Dscho if he likes doing so, but it does sound
> like a waste of talent.
> 

I contribute when I can for small projects, it looks I could help with some of 
those sparing Dscho some brain cells.






  reply	other threads:[~2019-11-13  5:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-09  2:00 Should we auto-close PRs on git/git? Emily Shaffer
2019-11-09  4:55 ` Junio C Hamano
2019-11-13  5:29   ` Stephen Smith [this message]
2019-11-12 19:11 ` Johannes Schindelin
2019-11-13  1:10   ` Jeff King
2019-11-13 12:04     ` Johannes Schindelin
2019-11-14  7:41       ` Jeff King
2019-11-14 23:03         ` Johannes Schindelin
2019-11-18 18:37           ` GitGitGadget on git/git, was " Johannes Schindelin
2019-11-21 10:54             ` Jeff King
2019-11-22 13:50               ` Johannes Schindelin
2019-11-22 14:43                 ` Johannes Schindelin
2019-11-25 14:30                 ` Jeff King
2019-11-26 20:55                   ` Johannes Schindelin
2019-11-26 21:56                     ` Eric Wong
2019-11-26 22:22                       ` Johannes Schindelin
2019-11-26 22:40                         ` Eric Wong
2019-11-26 22:52                           ` Johannes Schindelin
2019-11-26 23:58                             ` Eric Wong
2019-11-27  1:52                       ` Junio C Hamano
2019-11-27  2:37                         ` Eric Wong
2019-11-13 21:09   ` Emily Shaffer

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=11925817.qcmArAFNWq@thunderbird \
    --to=ischis2@cox.net \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.