From: Jakub Narebski <jnareb@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, David Miller <davem@davemloft.net>,
Jakub Narebski <jnareb@gmail.com>
Subject: Re: format-patch on permission change gives empty patch
Date: Thu, 07 Oct 2010 03:05:07 -0700 (PDT) [thread overview]
Message-ID: <m3eic2fher.fsf@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimA4jrDXmfJp2em34fj6b1sj9kdEyZ_xPTzqcEN@mail.gmail.com>
Sverre Rabbelier <srabbelier@gmail.com> writes:
> On Thu, Oct 7, 2010 at 06:40, Junio C Hamano <gitster@pobox.com> wrote:
> > (2) Treat "rebase" as a way to reproduce history faithfully, even an
> > unreasonable one. We could teach "--allow-empty" to "am", and
> > rewrite the pipeline as "format-patch --always | am --allow-empty" to
> > implement it.
>
> Wouldn't we then have to keep adding options for other corner cases?
> Perhaps a '--plumbing' flag that makes format-patch behave sanely
> (e.g., also do stuff like, turn off color and whatnot) and that makes
> 'git am' accept everything it knows how to understand?
Hmmm... doesn't rebase pipeline use "format-patch --rebasing" (where
'--rebasing' is internal option deliberately left undocumented)?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-10-07 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 0:37 format-patch on permission change gives empty patch David Miller
2010-10-07 0:40 ` David Miller
2010-10-07 4:13 ` Junio C Hamano
2010-10-07 4:40 ` Junio C Hamano
2010-10-07 8:15 ` Sverre Rabbelier
2010-10-07 10:05 ` Jakub Narebski [this message]
2010-10-07 10:12 ` Sverre Rabbelier
2010-10-07 19:06 ` Nicolas Pitre
2010-10-07 20:29 ` Junio C Hamano
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://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3eic2fher.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@gmail.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/mirrors/git.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).