emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: rpgoldman@real-time.com
Cc: Carsten Dominik <dominik@uva.nl>,
	emacs-orgmode@gnu.org, "Robert P. Goldman" <rpgoldman@sift.info>
Subject: Re: Orgmode[PATCH 4/4] Add handling of blockquote and output formats that must be flowed.
Date: Thu, 29 Apr 2010 14:08:46 -0400	[thread overview]
Message-ID: <87r5lyqggh.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <4BD9C10A.6040504@real-time.com> (Robert Goldman's message of "Thu\, 29 Apr 2010 12\:25\:30 -0500")

Robert Goldman <rpgoldman@real-time.com> writes:

> A quick follow-up --- I got into trouble by sending patches computed
> versus origin/master.  It turns out that this is not what I (or anyone
> else, I would have thought) wants.  What I want is to get patches
> relative to the merge commit that brings together my local commits and
> origin/master.  Is there a common way to encourage git to do that?

Hi Robert.

Just as a quick test I branched 10 commits back in origin/master
with

git checkout -b foo origin/master~10

and then created a couple of throw-away commits for format-patch to play
with (by editing and committing lisp/ChangeLog)

My history now looks something like this:


 o -- o -- B -- o -- o -- o -- ... -- o -- o -- A origin/master
            \
             X -- Y  foo

From anywhere in the history I can do

git format-patch origin/master..foo

and I get only the X and Y commits created as patches.  You can
experiment with the git log command instead of format-patch to show the
commits you get.  Basically it lists the commits not in origin/master on
the foo branch.

If you happen to be at foo (commit Y) you can omit the second branch
name since HEAD is assumed so origin/master..foo is the same as
origin/master..

HTH,

Bernt

  reply	other threads:[~2010-04-29 18:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 21:39 org-export-generic patch Robert P. Goldman
2010-04-28 21:39 ` [PATCH 4/4] Add handling of blockquote and output formats that must be flowed Robert P. Goldman
2010-04-29 13:54   ` Orgmode[PATCH " Wes Hardaker
2010-04-29 13:58     ` Carsten Dominik
2010-04-29 15:05       ` Robert Goldman
2010-04-29 17:00         ` Bernt Hansen
2010-04-29 17:25           ` Robert Goldman
2010-04-29 18:08             ` Bernt Hansen [this message]
2010-04-29 15:00     ` Robert Goldman
2010-04-30 14:51       ` Wes Hardaker
2010-04-30 15:15         ` Robert Goldman
2010-04-30 15:28           ` Carsten Dominik
2010-04-30 15:45             ` Robert Goldman
2010-04-29 10:44 ` org-export-generic patch Carsten Dominik

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r5lyqggh.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=rpgoldman@real-time.com \
    --cc=rpgoldman@sift.info \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).