From: Alp Toker <alp@atoker•com>
To: Junio C Hamano <junkio@cox•net>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Fix some doubled word typos
Date: Mon, 10 Jul 2006 02:42:43 +0100 [thread overview]
Message-ID: <44B1B093.9000201@atoker.com> (raw)
In-Reply-To: <7vodvye10h.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Actually, I am a bit more careful than that ;-).
>
> I have split your patch into two, and applied the part that
> applicable to "master" first. The tip of ew/svn topic branch (I
> do not publish topic branch tips) have two patches that are
> still not in even "pu", and one of these two patches is your
> Documentation/git-svn.txt patch. These two will appear in
> "next" hopefully soon -- I just haven't gotten around to them.
I hadn't realised that git-svn work was happening on a topic branch. In
light of that, it makes perfect sense to split out the commit as you
did. It's good to hear that git isn't just truncating patches.
Cheers.
next prev parent reply other threads:[~2006-07-10 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 9:36 [PATCH] Fix some doubled word typos Alp Toker
2006-07-09 9:36 ` [PATCH] Fix typos involving the word 'commit' Alp Toker
2006-07-10 0:32 ` [PATCH] Fix some doubled word typos Alp Toker
2006-07-10 0:50 ` Junio C Hamano
2006-07-10 1:42 ` Alp Toker [this message]
2006-07-10 2:04 ` Junio C Hamano
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=44B1B093.9000201@atoker.com \
--to=alp@atoker$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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