From: James Morris <jmorris@namei.org>
To: Eric Paris <eparis@parisplace.org>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
vyekkirala@trustedcs.com, cxzhang@watson.ibm.com,
sds@tycho.nsa.gov
Subject: Re: [PATCH] Add xfrm policy change auditing to pfkey_spdget
Date: Thu, 8 Mar 2007 12:12:04 -0500 (EST) [thread overview]
Message-ID: <Line.LNX.4.64.0703081159490.9412@d.namei> (raw)
In-Reply-To: <1173370815.31047.134.camel@localhost.localdomain>
On Thu, 8 Mar 2007, Eric Paris wrote:
> which didn't have my fix up because i didn't commit it to my local
> branch. Is there a better way to get a diff between my miller tree and
> 'everything in the branch I have checked out even if it is not
> committed'?
I'd suggest you commit all your changes in local branches, then export
them as emails via git-format-patch for posting.
Something like:
davem-upstream [1]
+- for-davem [2]
+- for-davem-prep [3]
Do all of your work in [3], so you can manage the queue of patches there
before merging/applying them into [2] as a final patch series.
So, if one of the commits in [3] needs fixing, you can, for example,
export commits up to that with git-format-patch, git-reset --hard to the
broken commit, fix, compile, test then reapply the exported commits.
Then, once it's all ready, merge into [2] (or export & apply to avoid
merge commits).
This is just one possible workflow. There are probably several better.
- James
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2007-03-08 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 18:51 Eric Paris
2007-03-05 15:59 ` Venkat Yekkirala
2007-03-06 0:37 ` James Morris
2007-03-07 23:43 ` David Miller
2007-03-08 0:07 ` David Miller
2007-03-08 16:20 ` Eric Paris
2007-03-08 17:12 ` James Morris [this message]
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=Line.LNX.4.64.0703081159490.9412@d.namei \
--to=jmorris@namei.org \
--cc=cxzhang@watson.ibm.com \
--cc=davem@davemloft.net \
--cc=eparis@parisplace.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=vyekkirala@trustedcs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome