All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's in git.git (Aug 2009, #01; Wed, 05)
Date: Fri, 7 Aug 2009 01:17:59 +0200	[thread overview]
Message-ID: <20090806231759.GC12924@vidovic> (raw)
In-Reply-To: <MEhvdM_GHnyaFj9ZU3lxKS47vmOk5BKslGm0FxkE_lg0SQT5Zx6KhA@cipher.nrlssc.navy.mil>

The 06/08/09, Brandon Casey wrote:

> I think we should at least do this to fall back to mbox format:
> 
> diff --git a/git-am.sh b/git-am.sh
> index d64d997..94fa9c9 100755
> --- a/git-am.sh
> +++ b/git-am.sh
> @@ -187,6 +187,7 @@ check_patch_format () {
>  				patch_format=stgit
>  				;;
>  			*)
> +				patch_format=mbox
>  				;;
>  			esac
>  			;;

This is even better that all my crap. But I think we should squash
this:

---
 git-am.sh |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/git-am.sh b/git-am.sh
index 94fa9c9..e8ec8d7 100755
--- a/git-am.sh
+++ b/git-am.sh
@@ -254,9 +254,6 @@ split_patches () {
                this=
                msgnum=
                ;;
-       *)
-               clean_abort "Patch format $patch_format is not supported."
-               ;;
        esac
 }


-- 
Nicolas Sebrecht

  reply	other threads:[~2009-08-06 23:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 22:04 What's in git.git (Aug 2009, #01; Wed, 05) Junio C Hamano
2009-08-06 22:24 ` Brandon Casey
2009-08-06 23:17   ` Nicolas Sebrecht [this message]
2009-08-06 23:28     ` Nicolas Sebrecht
2009-08-07  1:08   ` [PATCH 1/3] t4150-am: demonstrate git-am's failure to handle some patch emails Brandon Casey
2009-08-07  1:08     ` [PATCH 2/3] mailinfo: allow individual e-mail files as input Brandon Casey
2009-08-07  1:08       ` [PATCH 3/3] git-am: print fair error message when format detection fails Brandon Casey
2009-08-07  1:18       ` [PATCH 2/3] mailinfo: allow individual e-mail files as input Jeff King
2009-08-07  1:21         ` Brandon Casey
2009-08-07  1:27       ` [PATCH v2] " Brandon Casey
2009-08-07  1:52         ` [PATCH v2] " Nicolas Sebrecht
2009-08-07  1:56           ` Nicolas Sebrecht
2009-08-07  2:05             ` Brandon Casey
2009-08-07  2:31               ` Nicolas Sebrecht
2009-08-07  2:49                 ` Brandon Casey
2009-08-07  4:39                   ` Nicolas Sebrecht
2009-08-07  5:25                     ` Junio C Hamano
2009-08-07  2:30           ` Brandon Casey
2009-08-07  1:36       ` [PATCH 2/3] " Nicolas Sebrecht
2009-08-07  1:59         ` Brandon Casey
2009-08-07  3:37       ` [PATCH 2/3] " Junio C Hamano
2009-08-07  3:33   ` What's in git.git (Aug 2009, #01; Wed, 05) Nanako Shiraishi
2009-08-07  3:55     ` Junio C Hamano
2009-08-07 14:01     ` Brandon Casey

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=20090806231759.GC12924@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=brandon.casey.ctr@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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.