Re: [PATCH] Fix some doubled word typos

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Fix some doubled word typos

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:33

Alp Toker [off-list ref] writes:
My patch was made against the 'next' branch, where the file had
recently been moved to Documentation/git-svn.txt, but it was applied
to the 'master' branch where the file still exists at
contrib/git-svn/git-svn.txt as it has not yet been moved.
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.

Re: [PATCH] Fix some doubled word typos

From: Alp Toker <hidden>
Date: 2016-06-15 22:42:33

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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help