From: Junio C Hamano <junkio@cox.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Reference git-check-ref-format in git-branch.
Date: Sun, 21 May 2006 02:07:05 -0700 [thread overview]
Message-ID: <7vhd3jzqyu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060521015446.GA7605@spearce.org> (Shawn Pearce's message of "Sat, 20 May 2006 21:54:46 -0400")
Shawn Pearce <spearce@spearce.org> writes:
> Sorry about this patch being built on pu. It clearly has no
> relationship to current pu, but the new -l appears in the hunk
> below...
"am -3 -s -u" is how I handle patches anyway, and it did not
have much trouble backporting it to the tip of "master".
prev parent reply other threads:[~2006-05-21 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 1:54 [PATCH] Reference git-check-ref-format in git-branch Shawn Pearce
2006-05-21 9:07 ` Junio C Hamano [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=7vhd3jzqyu.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).