Re: [PATCH] Make "git checkout <branch> <path>" work when <path> is a directory.

Previous thread: "git fmt-merge-msg" SIGSEGV by Linus Torvalds on Friday, November 17, 2006 - 2:57 am. (1 message)

Next thread: Re: git-PS1 bash prompt setting by Nicolas Vilz on Friday, November 17, 2006 - 4:38 am. (3 messages)
To: Michael K. Edwards <medwards.linux@...>
Cc: Junio C Hamano <junkio@...>, <git@...>
Date: Friday, November 17, 2006 - 4:15 am

Actually it is not pushed out anywhere yet but will appear on
both 'maint' and 'master' along with other post 1.4.4 fixes and
will be contained in the 1.4.4.1 maintenance release.

The role of each branch at my public repository is desribed in
this message:

Message-ID: <7vk62qhy4k.fsf@assigned-by-dhcp.cox.net>
http://article.gmane.org/gmane.comp.version-control.git/29951

In general, if your changes and fixes are applicable in
isolation to "master", it is most appropriate to send patches
against "master". If you are following up a topic that is
cooking in "next" (or "pu"), then basing your patch on "master"
is obviously a bad idea and a patch that applies on "next" (or
"pu") would be more appropriate. If you can make the patch
against the tip of the specific topic that would be even better
but it generally is more work for you, so I usually do not ask
that to contributors.

-

Previous thread: "git fmt-merge-msg" SIGSEGV by Linus Torvalds on Friday, November 17, 2006 - 2:57 am. (1 message)

Next thread: Re: git-PS1 bash prompt setting by Nicolas Vilz on Friday, November 17, 2006 - 4:38 am. (3 messages)