All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Daudt <me@ikke.info>
To: Stephen & Linda Smith <ischis2@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Mailsplit
Date: Fri, 7 Sep 2018 17:15:43 +0200	[thread overview]
Message-ID: <20180907151543.GE27205@alpha> (raw)
In-Reply-To: <6663238.U5hdlisbr1@thunderbird>

On Wed, Sep 05, 2018 at 09:17:29PM -0700, Stephen & Linda Smith wrote:
> I thought I would use "git mailsplit" to split a mbox file (which downloaded 
> from public inbox) so that I could attemp to resurrect a patch series for from 
> a year ago.  
> 
> The motivation is that I downloaded the series [1] and applied to a tag from 
> about the time period that the patch was sent out [2].  
> 
> The "git am -3 patch.mbox  quit 2/3 of the way though.   I resolved the fix. 
> and ran "git am --continue" which didn't apply the rest of the patches in the 
> mbox.
> 
> So two questions:
> 1)  why would git version 2.18.0 not appear to continue applying the patches.   
> 
> 2) where do I find the command "git mailsplit".   The onlything in my 
> installed tree is:
> 
> 	$ find  /usr/local/ -name '*mailsplit*'
> 	/usr/local/share/doc/git-doc/git-mailsplit.txt
> 	/usr/local/share/doc/git-doc/git-mailsplit.html
> 	/usr/local/share/man/man1/git-mailsplit.1
> 	/usr/local/libexec/git-core/git-mailsplit

This is the mailsplit command, and should be executed when running `git
mailsplit`. What does git --exec-dir return?

Kevin

  reply	other threads:[~2018-09-07 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-06  4:17 Mailsplit Stephen & Linda Smith
2018-09-07 15:15 ` Kevin Daudt [this message]
2018-09-07 17:09 ` Mailsplit Stephen & Linda Smith
  -- strict thread matches above, loose matches on Subject: below --
2018-09-06  6:07 Mailsplit Stephen & Linda Smith

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=20180907151543.GE27205@alpha \
    --to=me@ikke.info \
    --cc=git@vger.kernel.org \
    --cc=ischis2@cox.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.