From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH-fix] fetch/pull: short-hand notation for remote repositories.
Date: Sat, 16 Jul 2005 10:52:11 -0700 [thread overview]
Message-ID: <7vr7dyhc50.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0507161032410.19183@g5.osdl.org> (Linus Torvalds's message of "Sat, 16 Jul 2005 10:33:30 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> I already noticed the breakage, and fixed that a bit differently.
>
> Feel free to send an updated patch if you prefer your version after my
> commits have percolated out..
As an old timer, I always prefer "case" over "test", so the
version in your tree is actually better to me. Thanks for the
fix.
next prev parent reply other threads:[~2005-07-16 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 7:08 [PATCH] Documentation: packed GIT support commands Junio C Hamano
2005-07-15 7:59 ` [PATCH] Documentation: update tutorial to talk about push Junio C Hamano
2005-07-15 18:40 ` [PATCH] Documentation: pull, push, packing repository and working with others Junio C Hamano
2005-07-15 21:40 ` [PATCH] fetch/pull: support Cogito-style remote branch information Junio C Hamano
2005-07-15 22:42 ` Linus Torvalds
2005-07-15 23:12 ` Junio C Hamano
2005-07-16 7:16 ` [PATCH] fetch/pull: short-hand notation for remote repositories Junio C Hamano
2005-07-16 16:47 ` [PATCH-fix] " Junio C Hamano
2005-07-16 17:33 ` Linus Torvalds
2005-07-16 17:52 ` Junio C Hamano [this message]
2005-07-18 17:28 ` [PATCH] git-clone-script: store where we cloned from in .git/branches/origin Junio C Hamano
2005-07-18 17:29 ` [PATCH] tutorial: mention "git clone" records .git/branches/origin Junio C Hamano
2005-07-16 7:17 ` [PATCH] Documentation: describe short-hand used in fetch/pull Junio C Hamano
2005-07-16 3:54 ` [PATCH] Documentation: adjust cvsimport command line 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=7vr7dyhc50.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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).