From: Joe Perches <joe@perches.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: git@vger.kernel.org
Subject: Re: git and linux kernel source
Date: Thu, 09 Aug 2007 18:59:47 -0700 [thread overview]
Message-ID: <1186711187.3073.75.camel@localhost> (raw)
In-Reply-To: <20070809231718.GH12875@fieldses.org>
On Thu, 2007-08-09 at 19:17 -0400, J. Bruce Fields wrote:
> > Is there a way to separate the resultant single patch into multiple
> > patches by subdirectory? Perhaps some git-rev-parse option?
> Something like
> for each sub/dir:
> git add sub/dir
> git commit -m "use bar not foo in sub/dir"
> should do it. (Of course, in the particular case above the patches you
> ended up with probably wouldn't compile individually.)
Nor would it likely survive a git bisect, but it's a start.
My goal is to eventually commit by maintainer.
Thanks, Joe
next prev parent reply other threads:[~2007-08-10 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 23:11 git and linux kernel source Joe Perches
2007-08-09 23:17 ` J. Bruce Fields
2007-08-10 1:59 ` Joe Perches [this message]
2007-08-13 15:27 ` J. Bruce Fields
2007-08-13 15:32 ` Rogan Dawes
2007-08-13 15:38 ` J. Bruce Fields
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=1186711187.3073.75.camel@localhost \
--to=joe@perches.com \
--cc=bfields@fieldses.org \
--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).