From: Elizabeth Ferdman <gnudevliz@gmail.com>
To: amsfield22@gmail.com, outreachy-kernel@googlegroups.com
Subject: Rebase/line wrap question
Date: Wed, 28 Sep 2016 12:25:08 -0700 [thread overview]
Message-ID: <20160928192508.GB2193@localhost> (raw)
Hey Alison,
I received some feedback from Greg that I want
to fix and I have a bunch of questions. The plus side is that maybe
some of the answers could go into the tutorial.
First he said "please wrap your changelog comments at 72 columns."
Is this something I add to my .vimrc? I've been using "git commit -m".
Is that causing the issue? I thought git commit messages were supposed
to be less than 50 chars anyway. I'm confused.
The other issue was that my commit didn't apply to his tree. He says
please rebase and resend. I think I need to do:
$ git fetch origin
$ git rebase origin/staging-testing
Then reformat the patch?
$ git format-patch -o ~/mypatches/ HEAD^
$ mutt -H <file>
So I don't need to uncommit/recommit?
Thanks,
Liz
next reply other threads:[~2016-09-28 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 19:25 Elizabeth Ferdman [this message]
2016-09-28 20:25 ` Rebase/line wrap question Alison Schofield
2016-09-28 21:49 ` Elizabeth Ferdman
2016-09-28 22:51 ` Alison Schofield
2016-09-29 6:19 ` [Outreachy kernel] " Greg KH
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=20160928192508.GB2193@localhost \
--to=gnudevliz@gmail.com \
--cc=amsfield22@gmail.com \
--cc=outreachy-kernel@googlegroups.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.