Jeff King f475e08edb lock_ref: inform callers of unavailable ref
One of the ways that locking might fail is that there is a
DF conflict between two refs (e.g., you want to lock
"foo/bar" but "foo" already exists). In this case, we return
an error, but there is no way for the caller to know the
specific problem.

This patch sets errno to ENOTDIR, which is the most sensible
code. It's what we would see if the refs were stored purely
in the filesystem (but these days we must check the
namespace manually due to packed refs).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-05-25 12:06:54 -07:00
2009-05-01 22:11:57 -07:00
2009-04-22 19:02:12 -07:00
2009-04-17 21:42:12 -07:00
2008-07-19 11:25:51 -07:00
2008-07-19 11:17:43 -07:00
2009-04-17 21:05:49 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-05-03 16:55:38 -07:00
2009-03-26 00:28:46 -07:00
2009-04-18 14:45:59 -07:00
2009-03-14 13:36:34 -07:00
2009-04-28 00:46:39 -07:00
2008-08-03 14:14:10 -07:00
2009-03-26 00:26:25 -07:00
2009-03-14 13:36:34 -07:00
2009-01-28 11:33:51 -08:00
2009-02-13 17:27:58 -08:00
2009-02-10 21:32:10 -08:00
2009-01-28 11:33:03 -08:00
2009-05-05 22:49:43 -07:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-04-29 16:50:21 -07:00
2009-05-16 22:41:18 -07:00
2009-03-17 18:54:31 -07:00
2008-11-02 16:36:40 -08:00
2009-04-22 19:02:12 -07:00
2009-04-12 16:46:40 -07:00
2009-04-27 09:54:24 -07:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2009-05-05 22:52:17 -07:00
2009-05-12 22:30:29 -07:00
2009-04-22 19:02:12 -07:00
2008-09-25 08:00:28 -07:00
2009-05-20 18:49:20 -07:00
2008-09-07 23:52:16 -07:00
2009-04-02 13:04:07 -07:00
2009-04-02 13:04:07 -07:00
2009-03-14 13:36:34 -07:00
2009-04-22 19:02:12 -07:00
2009-04-01 22:46:31 -07:00
2009-05-16 10:23:26 -07:00
2008-10-25 12:09:31 -07:00
2009-05-16 22:41:18 -07:00
2009-05-08 21:49:14 -07:00
2009-02-14 21:27:35 -08:00
2009-02-14 21:27:35 -08:00
2009-05-20 18:23:06 -07:00
2008-07-21 19:11:50 -07:00
2009-04-22 19:02:12 -07:00
2009-01-17 18:30:41 -08:00
2009-03-26 00:28:46 -07:00
2009-04-22 19:02:12 -07:00
2009-04-20 13:44:14 -07:00
2009-01-21 23:52:16 -08:00
2009-02-04 16:30:43 -08:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%