| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
This is a beginning of resurrecting the multi-head pulling support
for git-fetch-pack command. The git-fetch-script wrapper still
only knows about fetching a single head, without renaming, so it is
not very useful unless you directly call git-fetch-pack itself yet.
It also fixes a longstanding obsolete description of how the command
discovers the list of local commits.
|
|
|
|
|
| |
It really just boils down to one "get_remote_heads()" function, and a
common "struct ref" structure definition.
|
|
|
|
|
|
|
| |
This adds documentation for 'smarter pull' family of commands.
Signed-off-by: Junio C Hamano <junkio@cox.net>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
|
|
|
|
|
|
| |
Oh, well.. FC4 has UTF-8 as the default environment, and I applaud
that, but then it sometimes results in these characters that aren't
actually visible as a problem.
|
|
|
|
|
| |
With the socket case, the input and output fd's might end up being the same,
so we want to dup the other before we close either of them.
|
|
|
|
| |
git-clone-pack will want it too. Soon.
|
|
|
|
|
| |
It was a misguided attempt to mix fetching and cloning. I'll make
a separate clone thing.
|
|
|
|
|
|
|
| |
"git_path()" returns a static pathname pointer into the git directory
using a printf-like format specifier.
"head_ref()" works like "for_each_ref()", except for just the HEAD.
|
|
|
|
|
|
|
|
|
|
| |
It returns the result SHA1 on stdout, so you can do
remote=$(git-fetch-pack host:dir branchname)
and it will unpack the objects and "remote" will be the SHA1 name of the
branch on the other side. You can then save that off, or merge it, or
whatever.
|
|
|
|
| |
Now the only piece missing is actually generating the pack-file.
|
|
It's meant to be used by "git fetch" for the local and ssh case.
It doesn't actually do the fetching now, but it does discover the common
commit point.
|