From: Marc Singer <elf@synapse.com>
To: git <git@vger.kernel.org>
Subject: How do we import patches from non-git sources?
Date: Thu, 24 May 2007 07:30:10 -0700 [thread overview]
Message-ID: <1180017010.21181.2.camel@zealous.synapsedev.com> (raw)
It looks like it reduces to something very simple.
Git patches, as generated by git-format-patch, have a header with an
email address.
Cogito patches, as generated by cg-mkpatch, have no email address in the
header.
git-am doesn't like the cogito patches.
Is there a way to import patches that did not come from git? Remember
that we'd like to include the functionality of git-am that adds new
files to the index.
Cheers.
next reply other threads:[~2007-05-24 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 14:30 Marc Singer [this message]
2007-05-24 15:29 ` How do we import patches from non-git sources? Johannes Schindelin
2007-05-24 21:22 ` Yann Dirson
2007-05-25 11:24 ` Jakub Narebski
2007-05-24 21:45 ` Linus Torvalds
2007-06-06 17:37 ` Let me ask again: " Marc Singer
2007-06-06 17:54 ` J. Bruce Fields
2007-06-12 16:27 ` Marc Singer
2007-06-12 18:13 ` J. Bruce Fields
2007-06-14 1:45 ` Marc Singer
2007-06-06 17:58 ` Matthieu Moy
2007-06-06 18:18 ` Jon Loeliger
2007-06-14 1:49 ` Marc Singer
2007-06-14 7:53 ` Matthieu Moy
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=1180017010.21181.2.camel@zealous.synapsedev.com \
--to=elf@synapse.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).