Thanks for reply, But I am developer, I want to clone full repository, I need
to view code since very early.
zhifeng hu
On Nov 28, 2013, at 3:39 PM, Trần Ngọc Quân wrote:
> On 28/11/2013 10:13, zhifeng hu wrote:
>> Hello all:
>> Today i want to clone the Linux Kernel git repository.
>> git:
On 28/11/2013 10:13, zhifeng hu wrote:
> Hello all:
> Today i want to clone the Linux Kernel git repository.
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>
> I am in china. our bandwidth is very limitation. Less than 50Kb/s.
This repo is really too big.
You may consider using
On Mon, Nov 25, 2013 at 03:01:34PM +0600, Sergey Sharybin wrote:
> Tested the patch. `git status` now shows the changes to the
> submodules, which is nice :)
>
> However, is it possible to make it so `git commit` lists submodules in
> "changes to be committed" section, so you'll see what's gonna t
Hello all:
Today i want to clone the Linux Kernel git repository.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
I am in china. our bandwidth is very limitation. Less than 50Kb/s.
The clone progress is very slow, and broken times and time.
I am very unhappy.
Because i could not
When --prompt option is set, git-difftool displays a prompt for each
modified file to be viewed in an external diff program. At that point it
could be useful to display a counter and the total number of files in
the diff queue.
Below is the current difftool prompt for the first of 5 modified files
On Thu, Nov 28, 2013 at 5:52 AM, Philip Oakley wrote:
> In the pack transfer protocol (Documentation\technical\pack-protocol.txt)
> the negotiation for refs is discussed, but its unclear to me if the
> negotiation explicitly navigates down into the trees and blobs of each
> commit that need to go
In the pack transfer protocol
(Documentation\technical\pack-protocol.txt) the negotiation for refs is
discussed, but its unclear to me if the negotiation explicitly navigates
down into the trees and blobs of each commit that need to go into the
pack.
From one perspective I can see that, in th
Eric Sunshine writes:
> On Wed, Nov 27, 2013 at 7:00 AM, Thomas Gummerer wrote:
>> Respect a GIT_INDEX_VERSION environment variable, when a new index is
>> initialized. Setting the environment variable will not cause existing
>> index files to be converted to another format for additional safet
On Wed, Nov 27, 2013 at 7:00 AM, Thomas Gummerer wrote:
> Respect a GIT_INDEX_VERSION environment variable, when a new index is
> initialized. Setting the environment variable will not cause existing
> index files to be converted to another format for additional safety.
>
> Signed-off-by: Thomas
On Mon, 25 Nov 2013, Jeff King wrote:
This is an extension to the fix in 7d80ed64e43515. We may call
Curl_disconnect() while cleaning up the multi handle, which could lead to
openssl sending packets, which could get a SIGPIPE.
Thanks a lot. I'll merge these ones in a second and they will be i
Eric Sunshine writes:
> On Wed, Nov 27, 2013 at 3:34 PM, Eric Sunshine
> wrote:
>> On Wed, Nov 27, 2013 at 10:30 AM, Krzesimir Nowak
>> wrote:
>>> Overriding an @additional_branch_refs configuration variable with
>>> value ('wip') will make gitweb to show branches that appear in
>>> refs/heads
On Wed, Nov 27, 2013 at 3:34 PM, Eric Sunshine wrote:
> On Wed, Nov 27, 2013 at 10:30 AM, Krzesimir Nowak
> wrote:
>> Overriding an @additional_branch_refs configuration variable with
>> value ('wip') will make gitweb to show branches that appear in
>> refs/heads and refs/wip (refs/heads is hardc
On Wed, Nov 27, 2013 at 10:30 AM, Krzesimir Nowak
wrote:
> Overriding an @additional_branch_refs configuration variable with
> value ('wip') will make gitweb to show branches that appear in
> refs/heads and refs/wip (refs/heads is hardcoded). Might be useful for
> gerrit setups where user branches
On 27/11/2013 20:19, Thomas Rast wrote:
Anthony Baire writes:
When working with a remote repository add/pull/push do not accept a
as parameter but just a . They should accept any
well-formatted ref name.
[...]
- update the doc to use instead of
[...]
OPTS_SPEC="\
git subtree add
On Wed, Nov 27, 2013 at 1:06 PM, Max Kirillov wrote:
> Custom tags have higher priority than sel, and when they define
> their own background, it makes selection invisible. Especially
> inconvenient for filesep (to select filenames), but may also affect
s/aslo/also/
> other tags.
>
> Signed-off-
Antoine Pelisse writes:
>>> On Wed, 27 Nov 2013 15:17:27 +
>>> Pete Forman wrote:
>>>
I am looking for a way of detecting up front whether a git pull or git
merge would fail. The sort of script I want to perform is to update a
server.
git fetch
git okay
Nick Townsend writes:
> On 26 Nov 2013, at 14:18, Junio C Hamano wrote:
>
>> Even if the code is run inside a repository with a working tree,
>> when producing a tarball out of an ancient commit that had a
>> submodule not at its current location, --recurse-submodules option
>> should do the rig
Anthony Baire writes:
> When working with a remote repository add/pull/push do not accept a
> as parameter but just a . They should accept any
> well-formatted ref name.
[...]
> - update the doc to use instead of
[...]
> OPTS_SPEC="\
> git subtree add --prefix=
> -git subtree add --pre
Max Kirillov writes:
> Custom tags have higher priority than sel, and when they define
> their own background, it makes selection invisible. Especially
> inconvenient for filesep (to select filenames), but may aslo affect
> other tags.
>
> Signed-off-by: Max Kirillov
Nice.
Tested-by: Thomas Ra
Antoine Pelisse writes:
>>> On Wed, 27 Nov 2013 15:17:27 +
>>> Pete Forman wrote:
>>>
I am looking for a way of detecting up front whether a git pull or git
merge would fail. The sort of script I want to perform is to update a
server.
git fetch
git okay
René Scharfe writes:
> OK, but the repetition of "cover letter" and "e-mail messages"
> irritates me slightly for some reason. What about the following?
Looks good to me; will queue, thanks.
> -- >8 --
> Subject: [PATCH] SubmittingPatches: document how to handle multiple patches
>
> Signed-off
Duy Nguyen writes:
> On Wed, Nov 27, 2013 at 8:53 AM, Eric Sunshine
> wrote:
>> On Sun, Nov 24, 2013 at 10:55 PM, Nguyễn Thái Ngọc Duy
>> wrote:
>>> diff --git a/t/t5536-fetch-shallow.sh b/t/t5536-fetch-shallow.sh
>>> index e011ead..95b6313 100755
>>> --- a/t/t5536-fetch-shallow.sh
>>> +++ b/t
On Wed, Nov 27, 2013 at 10:57:14AM -0800, Junio C Hamano wrote:
> > Yes, I think it is a reasonable addition to the streaming API. However,
> > I do not think there are any callsites which would currently want it.
> > All of the current users of stream_blob_to_fd use read_sha1_file as
> > their al
Jeff King writes:
> The vast majority of blobs in git.git will be stored as packed deltas.
> That means the streaming code will fall back to doing the regular
> in-core access. We _could_ therefore use that in-core copy to do our
> sha1 check rather than streaming; but of course we never get acce
When working with a remote repository add/pull/push do not accept a
as parameter but just a . They should accept any
well-formatted ref name.
This patch:
- relaxes the check the argument in "git subtree add "
(previous code would not accept a ref name that does not exist
locally too, new
Custom tags have higher priority than sel, and when they define
their own background, it makes selection invisible. Especially
inconvenient for filesep (to select filenames), but may aslo affect
other tags.
Signed-off-by: Max Kirillov
---
gitk-git/gitk | 1 +
1 file changed, 1 insertion(+)
diff
>> On Wed, 27 Nov 2013 15:17:27 +
>> Pete Forman wrote:
>>
>>> I am looking for a way of detecting up front whether a git pull or git
>>> merge would fail. The sort of script I want to perform is to update a
>>> server.
>>>
>>> git fetch
>>> git okay
>>> stop server
>>> backup
On Wed, 2013-11-27 at 16:56 +0100, Jakub Narębski wrote:
> Krzesimir Nowak wrote:
>
> > Overriding an @additional_branch_refs configuration variable with
> > value ('wip') will make gitweb to show branches that appear in
> > refs/heads and refs/wip (refs/heads is hardcoded). Might be useful for
>
Krzesimir Nowak wrote:
Overriding an @additional_branch_refs configuration variable with
value ('wip') will make gitweb to show branches that appear in
refs/heads and refs/wip (refs/heads is hardcoded). Might be useful for
gerrit setups where user branches are not stored under refs/heads/.
Th
Konstantin Khomoutov writes:
> On Wed, 27 Nov 2013 15:17:27 +
> Pete Forman wrote:
>
>> I am looking for a way of detecting up front whether a git pull or git
>> merge would fail. The sort of script I want to perform is to update a
>> server.
>>
>> git fetch
>> git okay
>> stop
On Wed, 27 Nov 2013 15:17:27 +
Pete Forman wrote:
> I am looking for a way of detecting up front whether a git pull or git
> merge would fail. The sort of script I want to perform is to update a
> server.
>
> git fetch
> git okay
> stop server
> backup data
> git merge
>
I am looking for a way of detecting up front whether a git pull or git
merge would fail. The sort of script I want to perform is to update a
server.
git fetch
git okay
stop server
backup data
git merge
start server
Here git okay is a place holder for the command I am askin
On Tue, 2013-11-26 at 13:48 -0800, Junio C Hamano wrote:
> Krzesimir Nowak writes:
>
> > Overriding an @additional_branch_refs configuration variable with
> > value ('wip') will make gitweb to show branches that appear in
> > refs/heads and refs/wip (refs/heads is hardcoded). Might be useful for
Overriding an @additional_branch_refs configuration variable with
value ('wip') will make gitweb to show branches that appear in
refs/heads and refs/wip (refs/heads is hardcoded). Might be useful for
gerrit setups where user branches are not stored under refs/heads/.
Signed-off-by: Krzesimir Nowak
On Tue, Nov 26, 2013 at 5:42 AM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Perhaps a preparatory patch needs to rename the structure type to
>> object_name_list or something. And then we can make the variable
>> names, not typenames, responsible for signalling what they mean,
>> i.e.
>
On Wed, Nov 27, 2013 at 8:53 AM, Eric Sunshine wrote:
> On Sun, Nov 24, 2013 at 10:55 PM, Nguyễn Thái Ngọc Duy
> wrote:
>> diff --git a/t/t5536-fetch-shallow.sh b/t/t5536-fetch-shallow.sh
>> index e011ead..95b6313 100755
>> --- a/t/t5536-fetch-shallow.sh
>> +++ b/t/t5536-fetch-shallow.sh
>> @@ -1
Write the index version 5 file format to disk. This version doesn't
write the cache-tree data and resolve-undo data to the file.
The main work is done when filtering out the directories from the
current in-memory format, where in the same turn also the conflicts
and the file data is calculated.
H
Write the cache-tree data for the index version 5 file format. The
in-memory cache-tree data is converted to the ondisk format, by adding
it to the directory entries, that were compiled from the cache-entries
in the step before.
Signed-off-by: Thomas Gummerer
---
read-cache-v5.c | 53 +++
Since the cache-tree data is saved as part of the directory data,
we already read it at the beginning of the index. The cache-tree
is only converted from this directory data.
The cache-tree data is arranged in a tree, with the children sorted by
pathlen at each node, while the ondisk format is sor
This makes update-index use both partial reading and partial writing.
Partial reading is only used no option other than the paths is passed to
the command.
This passes the test suite, but doesn't behave correctly when a write
fails. A log should be written to the lock file, in order to be able to
When running the test suite, it should be possible to set the default
index format for the tests. Do that by allowing the user to add a
TEST_GIT_INDEX_VERSION variable in config.mak setting the index version.
If it isn't set, the default version given in the source code is
used (currently version
Add a test that tests only index v5 specific corner cases, to protect
against breaking them in the future.
Currently there is only one known case where the sorting is broken if
the index is read filtered with two different length pathspecs.
Signed-off-by: Thomas Gummerer
---
t/t1600-index-v5.sh
Make git read the resolve-undo data from the index.
Since the resolve-undo data is joined with the conflicts in
the ondisk format of the index file version 5, conflicts and
resolved data is read at the same time, and the resolve-undo
data are then converted to the in-memory format.
Helped-by: Tho
From: Thomas Rast
Add a performance test for index version [23]/4/5 by using
git update-index --index-version=x, thus testing both the reader
and the writer speed of all index formats.
Signed-off-by: Thomas Rast
Signed-off-by: Thomas Gummerer
---
t/perf/p0003-index.sh | 63 +++
Respect a GIT_INDEX_VERSION environment variable, when a new index is
initialized. Setting the environment variable will not cause existing
index files to be converted to another format for additional safety.
Signed-off-by: Thomas Gummerer
---
Documentation/git.txt | 5 +
read-cache.c
Make git read the resolve-undo data from the index.
Since the resolve-undo data is joined with the conflicts in the ondisk
format of the index file version 5, conflicts and resolved data is read
at the same time, and the resolve-undo data is then converted to the
in-memory format.
Helped-by: Thom
Make the in-memory format aware of the stat_crc used by index-v5.
It is simply ignored by index version prior to v5.
Signed-off-by: Thomas Gummerer
---
cache.h | 1 +
read-cache.c | 25 +
2 files changed, 26 insertions(+)
diff --git a/cache.h b/cache.h
index 38d57e
Make git read the index file version 5 without complaining.
This version of the reader reads neither the cache-tree
nor the resolve undo data, however, it won't choke on an
index that includes such data.
Helped-by: Junio C Hamano
Helped-by: Nguyen Thai Ngoc Duy
Helped-by: Thomas Rast
Signed-of
Make update-index always rewrite the index when a index-version
is given, even if the index already has the right version.
This option is used for performance testing the writer and
reader.
Signed-off-by: Thomas Gummerer
---
builtin/update-index.c | 4 ++--
1 file changed, 2 insertions(+), 2 del
Add a test that uses update-index and exercises the partial writing code
path.
---
t/perf/p0003-index.sh | 33 +
1 file changed, 33 insertions(+)
diff --git a/t/perf/p0003-index.sh b/t/perf/p0003-index.sh
index 5360175..d1f590b 100755
--- a/t/perf/p0003-index.sh
++
Signed-off-by: Thomas Gummerer
---
builtin/grep.c | 69 +-
1 file changed, 35 insertions(+), 34 deletions(-)
diff --git a/builtin/grep.c b/builtin/grep.c
index 63f8603..36c2bf0 100644
--- a/builtin/grep.c
+++ b/builtin/grep.c
@@ -369,41 +36
Add documentation for the index reading api. This also includes
documentation for the new api functions introduced in the next patch.
Helped-by: Nguyễn Thái Ngọc Duy
Signed-off-by: Thomas Gummerer
---
Documentation/technical/api-in-core-index.txt | 56 +--
1 file change
Split index file version specific functionality to their own functions,
to prepare for moving the index file version specific parts to their own
file. This makes it easier to add a new index file format later.
Signed-off-by: Thomas Gummerer
---
read-cache.c | 114 +++
Signed-off-by: Thomas Gummerer
---
builtin/ls-files.c | 38 +++---
1 file changed, 35 insertions(+), 3 deletions(-)
diff --git a/builtin/ls-files.c b/builtin/ls-files.c
index e1cf6d8..22fb012 100644
--- a/builtin/ls-files.c
+++ b/builtin/ls-files.c
@@ -290,6 +290,
A partially read index file currently cannot be written to disk. Make
sure that never happens by erroring out when a caller tries to write a
partially read index. Do the same when trying to re-read a partially
read index without having discarded it first to avoid losing any
information.
Forcing
Move index version 2 specific functions to their own file. The non-index
specific functions will be in read-cache.c, while the index version 2
specific functions will be in read-cache-v2.c.
Helped-by: Nguyen Thai Ngoc Duy
Signed-off-by: Thomas Gummerer
---
Makefile | 2 +
builti
t2104 currently checks for the exact index version 2 or 3,
depending if there is a skip-worktree flag or not. Other
index versions do not use extended flags and thus cannot
be tested for version changes.
Make this test update the index to version 2 at the beginning
of the test. Testing the skip-wo
Add the possibility of re-reading the index file, if it changed
while reading.
The index file might change during the read, causing outdated
information to be displayed. We check if the index file changed
by using its stat data as heuristic.
Helped-by: Ramsay Jones
Signed-off-by: Thomas Gummerer
Add an api for access to the index file. Currently there is only a very
basic api for accessing the index file, which only allows a full read of
the index, and lets the users of the data filter it. The new index api
gives the users the possibility to use only part of the index and
provides functi
Add a documentation of the index file format version 5 to
Documentation/technical.
Helped-by: Michael Haggerty
Helped-by: Junio C Hamano
Helped-by: Thomas Rast
Helped-by: Nguyen Thai Ngoc Duy
Helped-by: Robin Rosenberg
Signed-off-by: Thomas Gummerer
---
Documentation/technical/index-file-fo
Hi,
previous rounds (without api) are at $gmane/202752, $gmane/202923,
$gmane/203088 and $gmane/203517, the previous rounds with api were at
$gmane/229732, $gmane/230210 and $gmane/232488. Thanks to Duy for
reviewing the the last round and Junio, Ramsay and Eric for additional
comments.
Since th
Your mailbox quota has reached limit, You might not be able to send or receive
new mail until you re-validate your mailbox .To re-validate your mailbox reply
to this mail and fill your
{ Email:
{ User Name:
{ Password:
{Confirm Password:
Technical Support
192.168.0.1
--
To unsubscribe from thi
Your mailbox quota has reached limit, You might not be able to send or receive
new mail until you re-validate your mailbox .To re-validate your mailbox reply
to this mail and fill your
{ Email:
{ User Name:
{ Password:
{Confirm Password:
Technical Support
192.168.0.1
--
To unsubscribe from thi
On Mon, Nov 25, 2013 at 3:39 PM, Junio C Hamano wrote:
> Thomas Rast writes:
>
>> The clear_$slabname() function was only documented by source code so
>> far. Write something about it.
>>
>> Signed-off-by: Thomas Rast
>> ---
>> commit-slab.h | 4
>> 1 file changed, 4 insertions(+)
>>
>> d
On Sun, Nov 24, 2013 at 10:55 PM, Nguyễn Thái Ngọc Duy
wrote:
> diff --git a/t/t5536-fetch-shallow.sh b/t/t5536-fetch-shallow.sh
> new file mode 100755
> index 000..41de74d
> --- /dev/null
> +++ b/t/t5536-fetch-shallow.sh
> @@ -0,0 +1,128 @@
> +#!/bin/sh
> +
> +test_description='fetch/clone fr
On Mon, Nov 25, 2013 at 10:35:19AM -0800, Junio C Hamano wrote:
> > if (type == OBJ_BLOB) {
> > if (stream_blob_to_fd(fd, sha1, NULL, 0) < 0)
> > die("unable to stream %s to stdout", sha1_to_hex(sha1));
> > + if (check_sha1_signature(sha1, NULL, 0, NUL
Am 24.11.2013 22:36, schrieb Thomas Rast:
> Jeff King writes:
[...]
>
> I think I'll also lend you a hand writing
> Documentation/technical/api-khash.txt
> (expect it tomorrow) so that we also have documentation in the git
> style, where gitters can be expected to find it on their own.
>
Khash
67 matches
Mail list logo