Skip to content

G
git

李少辉-开发者 / git
与 Fork 源项目一致

从无法访问的项目Fork

通知 2
Star 1
Fork 0
G
git

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 06 2月, 2014 1 次提交
  3. 15 7月, 2013 1 次提交
  5. 13 7月, 2013 1 次提交
  7. 23 6月, 2013 3 次提交
  9. 18 5月, 2013 1 次提交
  11. 02 2月, 2013 2 次提交
  13. 25 10月, 2012 1 次提交
  15. 21 9月, 2012 1 次提交
    • R
      clone --single: limit the fetch refspec to fetched branch · 31b808a0
      由 Ralf Thielow 提交于 
      After running "git clone --single", the resulting repository has the
usual default "+refs/heads/*:refs/remotes/origin/*" wildcard fetch
refspec installed, which means that a subsequent "git fetch" will
end up grabbing all the other branches.

Update the fetch refspec to cover only the singly cloned ref instead
to correct this.

That means:
If "--single" is used without "--branch" or "--mirror", the
fetch refspec covers the branch on which remote's HEAD points to.
If "--single" is used with "--branch", it'll cover only the branch
specified in the "--branch" option.
If "--single" is combined with "--mirror", then it'll cover all
refs of the cloned repository.
If "--single" is used with "--branch" that specifies a tag, then
it'll cover only the ref for this tag.
Signed-off-by: NRalf Thielow <ralf.thielow@gmail.com>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      31b808a0
  17. 31 5月, 2012 2 次提交
  19. 17 1月, 2012 1 次提交
  21. 09 1月, 2012 1 次提交
  23. 23 6月, 2011 1 次提交
    • J
      clone: accept config options on the command line · 84054f79
      由 Jeff King 提交于 
      Clone does all of init, "remote add", fetch, and checkout
without giving the user a chance to intervene and set any
configuration. This patch allows you to set config options
in the newly created repository after the clone, but before
we do any other operations.

In many cases, this is a minor convenience over something
like:

  git clone git://...
  git config core.whatever true

But in some cases, it can bring extra efficiency by changing
how the fetch or checkout work. For example, setting
line-ending config before the checkout avoids having to
re-checkout all of the contents with the correct line
endings.

It also provides a mechanism for passing information to remote
helpers during a clone; the helpers may read the git config
to influence how they operate.
Signed-off-by: NJeff King <peff@peff.net>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      84054f79
  25. 26 5月, 2011 1 次提交
  27. 20 3月, 2011 1 次提交
  29. 11 3月, 2011 1 次提交
    • J
      doc: drop author/documentation sections from most pages · 48bb914e
      由 Jeff King 提交于 
      The point of these sections is generally to:

  1. Give credit where it is due.

  2. Give the reader an idea of where to ask questions or
     file bug reports.

But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame.  For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.

So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.

Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
      48bb914e
  31. 06 11月, 2010 1 次提交
  33. 04 11月, 2010 1 次提交
  35. 07 10月, 2010 1 次提交
  37. 22 3月, 2010 1 次提交
  39. 25 2月, 2010 1 次提交
  41. 18 2月, 2010 2 次提交
    • J
      docs: don't talk about $GIT_DIR/refs/ everywhere · cc1b8d8b
      由 Jeff King 提交于 
      It is misleading to say that we pull refs from $GIT_DIR/refs/*, because we
may also consult the packed refs mechanism. These days we tend to treat
the "refs hierarchy" as more of an abstract namespace that happens to be
represented as $GIT_DIR/refs. At best, this is a minor inaccuracy, but at
worst it can confuse users who then look in $GIT_DIR/refs and find that it
is missing some of the refs they expected to see.

This patch drops most uses of "$GIT_DIR/refs/*", changing them into just
"refs/*", under the assumption that users can handle the concept of an
abstract refs namespace. There are a few things to note:

  - most cases just dropped the $GIT_DIR/ portion. But for cases where
    that left _just_ the word "refs", I changed it to "refs/" to help
    indicate that it was a hierarchy.  I didn't do the same for longer
    paths (e.g., "refs/heads" remained, instead of becoming
    "refs/heads/").

  - in some cases, no change was made, as the text was explicitly about
    unpacked refs (e.g., the discussion in git-pack-refs).

  - In some cases it made sense instead to note the existence of packed
    refs (e.g., in check-ref-format and rev-parse).
Signed-off-by: NJeff King <peff@peff.net>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      cc1b8d8b
    • S
      Add a "TEMPLATE DIRECTORY" section to git-init[1]. · d8a8488d
      由 Steven Drake 提交于 
      Create a more inoformative section to describe template directory and
refer to it in config.txt and with the '--template' option of git-init
and git-clone commands.
Signed-off-by: NSteven Drake <sdrake@xnet.co.nz>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      d8a8488d
  43. 29 12月, 2009 3 次提交
  45. 01 12月, 2009 1 次提交
  47. 22 10月, 2009 1 次提交
  49. 10 10月, 2009 1 次提交
    • J
      Documentation: clone: clarify discussion of initial branch · 33405be3
      由 Jonathan Nieder 提交于 
      When saying the initial branch is equal to the currently active
remote branch, it is probably intended that the branch heads
point to the same commit.  Maybe it would be more useful to a
new user to emphasize that the tree contents and history are the
same.

More important, probably, is that this new branch is set up so
that "git pull" merges changes from the corresponding remote
branch.  The next paragraph addresses that directly.  What the
reader needs to know to begin with is that (1) the initial branch
is your own; if you do not pull, it won't get updated, and that
(2) the initial branch starts out at the same commit as the
upstream.
Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      33405be3
  51. 14 9月, 2009 1 次提交
  53. 04 9月, 2009 1 次提交
  55. 27 8月, 2009 1 次提交
  57. 21 8月, 2009 1 次提交
    • J
      git clone: Add --recursive to automatically checkout (nested) submodules · e7fed18a
      由 Johan Herland 提交于 
      Many projects using submodules expect all submodules to be checked out
in order to build/work correctly. A common command sequence for
developers on such projects is:

	git clone url/to/project
	cd project
	git submodule update --init (--recursive)

This patch introduces the --recursive option to git-clone. The new
option causes git-clone to recursively clone and checkout all
submodules of the cloned project. Hence, the above command sequence
can be reduced to:

	git clone --recursive url/to/project

--recursive is ignored if no checkout is done by the git-clone.

The patch also includes documentation and a selftest.
Signed-off-by: NJohan Herland <johan@herland.net>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      e7fed18a
  59. 17 8月, 2009 1 次提交
    • J
      docs: describe impact of repack on "clone -s" · 13354f53
      由 Jeff King 提交于 
      The effects of repacking on a repository with alternates are a bit
subtle. The two main things users will want are:

  1. Not to waste disk space by accidentally copying objects which could
     be shared.

  2. Copying all objects explicitly to break the dependency on the source
     repo.

This patch describes both under the "clone -s" documentation. It makes
sense to put it there rather than in git-repack.txt for both cases.

For (1), we are warning the user who is using "clone -s" about what _not_
to do, so we need to get their attention when reading about "clone -s".

For (2), we are telling them how git-repack can be used to accomplish a
task, but until they know that git-repack is the right tool, they have no
reason to look at the repack documentation.
Signed-off-by: NJeff King <peff@peff.net>
Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      13354f53
  61. 09 5月, 2009 1 次提交
  63. 02 4月, 2009 1 次提交
  65. 10 10月, 2008 1 次提交