From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Omit patches that have already been merged from format-patch output.
Date: Tue, 13 Sep 2005 00:03:07 +1200 [thread overview]
Message-ID: <46a038f9050912050367418617@mail.gmail.com> (raw)
In-Reply-To: <7voe6yik0o.fsf@assigned-by-dhcp.cox.net>
On 9/12/05, Junio C Hamano <junkio@cox.net> wrote:
> Martin Langhoff <martin.langhoff@gmail.com> writes:
>
> > Strike that. PEBCAK: my branch entry was pointing to the wrong place. Sorry.
>
> Thanks for quick correction. Just from a curiosity, do you run
> GIT from the proposed updates branch? I am asking because that
> suspect git-format-patch change is supposed to be only in there.
I'm running git on ~5 different machines. On the box where I do my
development, I have both 'master' and 'pu' checkouts, but mostly
master. Elsewhere, I track master, with updates every few days, when
my gut feeling is that things aren't too risky. On the servers (add ~4
servers to the list), I deploy only tagged versions, usually from the
Debian package.
And it was a total PEBCAK. I had just pulled in your latest merges to
master and built/installed on a dev box, things were looking odd and I
jumped the gun badly. As you point out, I didn't even have the patch
in.
cheers,
martin
prev parent reply other threads:[~2005-09-12 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 8:52 git-rev-list and git-format-patch script oddness Martin Langhoff
2005-09-11 9:20 ` Johannes Schindelin
2005-09-11 20:32 ` [PATCH] Omit patches that have already been merged from format-patch output Junio C Hamano
2005-09-11 21:08 ` Martin Langhoff
2005-09-11 21:10 ` Martin Langhoff
2005-09-12 7:24 ` Martin Langhoff
2005-09-12 9:34 ` Martin Langhoff
2005-09-12 11:48 ` Junio C Hamano
2005-09-12 12:03 ` Martin Langhoff [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=46a038f9050912050367418617@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).