From: "Philip Oakley" <philipoakley@iee.org>
To: "Duy Nguyen" <pclouds@gmail.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Jeff King" <peff@peff.net>, "Stefan Beller" <sbeller@google.com>,
meta@public-inbox.org, git@vger.kernel.org,
"Eric Wong" <e@80x24.org>, "Jakub Narębski" <jnareb@gmail.com>
Subject: Re: Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path]
Date: Mon, 22 Aug 2016 21:38:07 +0100 [thread overview]
Message-ID: <B21604E7033C458EAC5EA0651CFEA8E9@PhilipOakley> (raw)
In-Reply-To: CACsJy8BG63oaLbw0f7try3OpzdphLC7UGAaJ=vgikEB36Pagqg@mail.gmail.com
From: "Duy Nguyen" <pclouds@gmail.com>
> On Mon, Aug 22, 2016 at 8:06 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> My point stands. We are way more uninviting to contributors than
>> necessary. And a huge part of the problem is that we require contributors
>> to send their patches inlined into whitespace-preserving mails.
>
> We probably can settle this in the next git survey with a new
> question: what's stopping you from contributing to git?
> --
One has to be careful that some of this is preaching to the choir.
Those who have difficulty won't be anywhere near the survey. Those that are
near the survey will have enough nouce to contribute to the level they
manage.
Also the argument here has started to be at cross purposes about the issues
vs the solutions.
I do note that dscho's patches now have the extra footer (below the three
dashes) e.g.
Published-As: https://github.com/dscho/git/releases/tag/cat-file-filters-v1
Fetch-It-Via: git fetch https://github.com/dscho/git cat-file-filters-v1
If say I used that, and sent my patch series via Outlook Express (<sigh>),
with it's white space damage, would those footers help once the content has
been reviewed (rather than white spacing style) in the applying the patch?
Even, Is there a way of accepting email that has HTML embedded by the
client, rather than [vger, etc.] simply deleting the email as 'not
acceptable'. Unless users can get past these sort of (to them) petty and
awkward restrictions, it's going to continue to be difficult to encourage
participation.
--
Philip
PS Sudden though about the 'Published-As: Fetch-It-Via: ' stuff. I don't
think we have a method of 'Fetch-As-A-Series' so that what is received from
the server (e.g. GitHub, as a git command equivalent) is just those
patches/commits in the series, and the recipient can then see if they apply
cleanly at the point they want to apply them? This would almost be a 'pack
file' that is all commit deltas, that can be given to say 'rebase' (or
'apply'). It could also be expanded back into an mbox format if required...
next prev parent reply other threads:[~2016-08-22 20:38 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:55 Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path] Stefan Beller
2016-08-16 17:10 ` Junio C Hamano
2016-08-16 17:20 ` Jeff King
2016-08-16 17:54 ` Junio C Hamano
2016-08-16 17:22 ` Stefan Beller
2016-08-16 17:47 ` Junio C Hamano
2016-08-16 20:44 ` Eric Wong
2016-08-16 20:56 ` Eric Wong
2016-08-18 12:42 ` Johannes Schindelin
2016-08-18 20:49 ` Eric Wong
2016-08-18 21:41 ` Junio C Hamano
2016-08-19 15:18 ` Johannes Schindelin
2016-08-19 15:30 ` Johannes Schindelin
2016-08-19 16:55 ` Stefan Beller
2016-08-19 22:35 ` Eric Wong
2016-08-22 13:38 ` Johannes Schindelin
2016-08-22 19:21 ` Jeff King
2016-08-19 22:35 ` Eric Wong
2016-08-22 13:18 ` Johannes Schindelin
2016-08-22 18:05 ` Jakub Narębski
2016-08-25 13:21 ` Johannes Schindelin
2016-08-28 18:23 ` Jakub Narębski
2016-08-29 10:46 ` Johannes Schindelin
2016-08-22 22:55 ` Eric Wong
2016-08-25 12:58 ` Johannes Schindelin
2016-08-27 22:38 ` Jakub Narębski
2016-08-28 8:36 ` Working with public-inbox.org Johannes Schindelin
2016-08-28 11:41 ` Jakub Narębski
2016-08-29 5:35 ` Johannes Schindelin
2016-08-19 15:03 ` Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path] Jeff King
2016-08-20 19:57 ` Jakub Narębski
2016-08-23 4:47 ` Arif Khokar
2016-08-24 15:34 ` Johannes Schindelin
2016-08-24 18:49 ` Eric Wong
2016-08-24 19:12 ` Jeff King
2016-08-24 19:27 ` Eric Wong
2016-08-25 3:40 ` Arif Khokar
2016-08-25 2:41 ` Arif Khokar
2017-02-10 16:10 ` Johannes Schindelin
2017-02-13 5:52 ` Arif Khokar
2017-02-13 14:37 ` Johannes Schindelin
2017-02-14 3:56 ` Arif Khokar
2017-02-14 3:59 ` Arif Khokar
2017-02-14 7:13 ` Eric Wong
2017-02-13 19:21 ` Junio C Hamano
2017-02-14 3:55 ` Arif Khokar
2017-02-14 4:41 ` Junio C Hamano
2017-02-14 5:09 ` Arif Khokar
2017-02-14 5:14 ` Jeff King
2016-08-22 13:06 ` Johannes Schindelin
2016-08-22 13:15 ` Duy Nguyen
2016-08-22 20:38 ` Philip Oakley [this message]
2016-08-24 13:04 ` Johannes Schindelin
2016-08-24 19:16 ` Eric Wong
2016-08-25 13:08 ` Johannes Schindelin
2016-08-25 3:57 ` Arif Khokar
2016-08-25 13:01 ` Johannes Schindelin
2016-08-25 23:14 ` Arif Khokar
2016-08-26 8:08 ` Johannes Schindelin
2016-08-27 22:26 ` Jakub Narębski
2016-08-28 8:38 ` Johannes Schindelin
2016-08-28 13:45 ` Announcing Git User's Survey 2016 [was: Working with public-inbox.org] Jakub Narębski
2016-09-09 13:06 ` Johannes Schindelin
2016-09-09 18:51 ` Jakub Narębski
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
List information: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B21604E7033C458EAC5EA0651CFEA8E9@PhilipOakley \
--to=philipoakley@iee.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=meta@public-inbox.org \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).