From: Arif Khokar <email@example.com> To: Johannes Schindelin <Johannes.Schindelin@gmx.de> Cc: Jakub Narębski <firstname.lastname@example.org>, Jeff King <email@example.com>, Stefan Beller <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, Eric Wong <email@example.com>, Arif Khokar <firstname.lastname@example.org> Subject: Re: Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path] Date: Mon, 13 Feb 2017 22:56:39 -0500 Message-ID: <email@example.com> (raw) In-Reply-To: <alpine.DEB.2.20.1702131533400.3496@virtualbox> On 02/13/2017 09:37 AM, Johannes Schindelin wrote: > Hi Arif, > > On Mon, 13 Feb 2017, Arif Khokar wrote: >> Thanks for the link. One thing that comes to mind that is that it may >> be better to just download the patches and then manually apply them >> afterwords rather than doing it in the script itself. Or at least add >> an option to the script to not automatically invoke git am. > > I actually had expected *you* to put in a little bit of an effort, too. In > fact, I was very disappointed that you did not even look into porting that > script to use public-inbox instead of GMane. I wasn't aware of that expectation. My idea was to use NNTP as a way to facilitate the development of a new git utility that would serve as the inverse of git-send-email (sort of like the relationship between git format-patch and git am), rather than using a IIRC, I had posted some proof-of-concept Perl code to do so back in August in <DM5PR17MB1353B99EBD5F4FD23360DD41D3ED0@DM5PR17MB1353.namprd17.prod.outlook.com> Looking at public-inbox now at the archives of this group, it appears that several of the messages I sent weren't archived for some reason (and I didn't see any more responses to what I posted at the time). The messages are accessible via NNTP when connecting to gmane though. Also, looking at the source of the message I referenced, it appears that my MUA decided to base64 encode the message for some reason (which may have resulted in it getting filtered by those who I sent the message to). I will look into this more now (given yours and Junio's responses). >> Getting back to the point I made when this thread was still active, I >> still think it would be better to be able to list the message-id values >> in the header or body of the cover letter message of a patch series >> (preferably the former) in order to facilitate downloading the patches >> via NNTP from gmane or public-inbox.org. That would make it easier >> compared to the different, ad-hoc, methods that exist for each email >> client. > > You can always do that yourself: you can modify your cover letter to > include that information. Certainly, but it would be nice to be able to have it done automatically by git format-patch (which I'll look into). > Note that doing this automatically in format-patch may not be appropriate, > as 1) the Message-ID could be modified depending on the mail client used > to send the mails I think the best approach would be not to make including the message-id values the default behavior. Specifying a new command-line option to enable that behavior should address those concerns I think. > and 2) it is not unheard of that a developer > finds a bug in the middle of sending a patch series, fixes that bug, and > regenerates the remainder of the patch series, completely rewriting those > Message-IDs. Perhaps, but should something like that not warrant a re-roll of sorts. That is, one should reply to the partial patch series stating that there is a bug that renders this particular patch (series) un-usable and the re-roll could be posted as a reply to the original cover letter? >> Alternatively, or perhaps in addition to the list of message-ids, a list >> of URLs to public-inbox.org or gmane messages could also be provided for >> those who prefer to download patches via HTTP. > > At this point, I am a little disinterested in a discussion without code. I > brought some code to the table, after all. If you have the time, please take a look at the message-id I referenced. If you need, I can re-post the proof-of-concept code.
next prev parent reply index Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-08-16 16:55 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 [this message] 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 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 publically 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: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --cc=Johannes.Schindelin@gmx.de \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
user/dev discussion of public-inbox itself Archives are clonable: git clone --mirror https://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.org/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox