From: "Ian Brown" <ianbrn@gmail.com>
To: git@vger.kernel.org
Subject: How to omit/alter the sigend-off line in a patch set?
Date: Mon, 16 Jun 2008 13:24:58 +0300 [thread overview]
Message-ID: <d0383f90806160324j3f1b2a09tbb4caa1e934c7635@mail.gmail.com> (raw)
Hello,
I am creating a patch set in this way:
I make a change in one file, than commit it. (git commit file1)
Then I make a change in a second file, than commit it. (git commit file1)
and so on.
Then I create a patch set thus:
git-format-patch -M -s -n -o patchdir origin
And a number of patch files are created, according to the number of commits
I had made.
Now, in each created patch file there is a line saying:
Signed-off-by: root <root@hostName.(none)>
Which is caused as I am doing this patches as root, and the machine name is
hostName (and the domain name is none).
Now, is there a way to cause git-format-patch to omit this
Signed-off-by: root <root@hostName.(none)> line ?
Or, altetnatively, is there a way to cause the git-format-patch to
generate a differnet
signed off by line (like signed off by ianbrn@gmail.com)?
I had tried using the --signoff option for git-format-patch , in
these two ways,
but got an error:
git-format-patch --signoff=ianbrn@gmail.com -M -n -o patchdir origin
fatal: unrecognized argument: --signoff=ianbrn@gmail.com
git-format-patch --signoff ianbrn@gmail.com -M -n -o patchdir origin
fatal: ambiguous argument 'ianbrn@gmail.com': unknown revision or path
not in the working tree.
Use '--' to separate paths from revisions
I also tried to use the -a flag for commit
git-commit -a ianbrn@gmail.com
but again it did not help either.
Any ideas?
Any help will be appreciated,
Regards,
Ian
next reply other threads:[~2008-06-16 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 10:24 Ian Brown [this message]
2008-06-16 11:26 ` How to omit/alter the sigend-off line in a patch set? Jakub Narebski
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=d0383f90806160324j3f1b2a09tbb4caa1e934c7635@mail.gmail.com \
--to=ianbrn@gmail.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).