Christian Couder writes:
> Hi,
>
> On Wed, Feb 10, 2016 at 10:31 AM, Matthieu Moy
> wrote:
>>
>> So, the first question is: are there volunteers to be GSoC mentors this
>> year?
>
> I can co-mentor this year too, with you or someone else.
> With you I think it will work out even if you have less
Most of the time, get_git_common_dir() returns an absolute path so
prefix is irrelevant. If it returns a relative path (e.g. from the
main worktree) then prefixing is required.
Noticed-by: Mike Hommey
Signed-off-by: Nguyễn Thái Ngọc Duy
---
On Fri, Feb 12, 2016 at 10:47 AM, Mike Hommey wrote:
Hi,
In a worktree, git rev-parse --git-common-dir returns the non
worktree-specific git directory. e.g. .git instead of
.git/worktrees/name. The problem is that while it returns the right
thing from a subdirectory of a worktree, it doesn't from a subdirectory
of the "main" work tree. In the latter
Adhere to the common coding style of Git and not check explicitly
for NULL throughout the file. There are still other occurrences in the
code base but that is usually inside of conditions with side effects.
Signed-off-by: Stefan Beller
---
submodule-config.c | 6 +++---
1 file changed, 3 inserti
This replaces origin/sb/submodule-parallel-update
and is based on origin/master
* broke out the patch for redirecting errors to stderr in "submodule update"
(Thanks Jonathan, Jacob)
* use git_config_int and manually check for less than 0.
(Thanks Junio)
* use an enum consistently now for subm
Currently submodule..update is only handled by git-submodule.sh.
C code will start to need to make use of that value as more of the
functionality of git-submodule.sh moves into library code in C.
Add the update field to 'struct submodule' and populate it so it can
be read as sm->update or from sm-
This allows to configure fetching and updating in parallel
without having the command line option.
This moved the responsibility to determine how many parallel processes
to start from builtin/fetch to submodule.c as we need a way to communicate
"The user did not specify the number of parallel proc
Reroute the error message for specified but initialized submodules
to stderr instead of stdout.
Signed-off-by: Stefan Beller
---
git-submodule.sh | 4 ++--
t/t7400-submodule-basic.sh | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/git-submodule.sh b/git-submodu
Expose possible parallelism either via the "--jobs" CLI parameter or
the "submodule.fetchJobs" setting.
By having the variable initialized to -1, we make sure 0 can be passed
into the parallel processing machine, which will then pick as many parallel
workers as there are CPUs.
Signed-off-by: Stef
Just pass it along to "git submodule update", which may pick reasonable
defaults if you don't specify an explicit number.
Signed-off-by: Stefan Beller
---
Documentation/git-clone.txt | 6 +-
builtin/clone.c | 19 +--
t/t7406-submodule-update.sh | 15 +
This introduces a new helper function in git submodule--helper
which takes care of cloning all submodules, which we want to
parallelize eventually.
Some tests (such as empty URL, update_mode=none) are required in the
helper to make the decision for cloning. These checks have been
moved into the C
Add the http.pinnedpubkey configuration option for public key
pinning. It allows any string supported by libcurl --
base64(sha256(pubkey)) or filename of the full public key.
Signed-off-by: Christoph Egger
---
Documentation/config.txt | 6 ++
http.c | 11 +++
2 fil
Daniel Stenberg writes:
> On Thu, 11 Feb 2016, Christoph Egger wrote:
>> +#if LIBCURL_VERSION_NUM >= 0x074400
>
> That should probably be 0x072c00 ...
This is, of course, right.
I used 7.44 / 0x072c00 as base because it has robust support for this
feature (including the sha256// variant). One co
On Thu, 2016-02-11 at 08:45 +0100, Michael Haggerty wrote:
> On 02/05/2016 08:44 PM, David Turner wrote:
> > From: Ronnie Sahlberg
> >
> > Add ref backend methods for:
> > resolve_ref_unsafe, verify_refname_available, pack_refs, peel_ref,
> > create_symref, resolve_gitlink_ref.
> >
> > Signed-of
On Thu, 2016-02-11 at 09:42 +0100, Michael Haggerty wrote:
> On 02/05/2016 08:44 PM, David Turner wrote:
> > From: Ronnie Sahlberg
> >
> > Signed-off-by: Ronnie Sahlberg
> > Signed-off-by: David Turner
> > ---
> > refs.c | 54
> > ++
On Monday, February 08, 2016 06:55:17 PM Stephen & Linda Smith wrote:
> > #!/bin/bash
> > mkdir test-repository || exit 1
> > cd test-repository
> > git init
> > echo "Initial contents, unimportant" > test-file
> > git add test-file
> > git commit -m "Initial commit"
> > echo "commit-1-state" > tes
On Tue, Feb 9, 2016 at 4:45 AM, Junio C Hamano wrote:
> Nguyễn Thái Ngọc Duy writes:
>
>> This series brings three new options to shallow clone/fetch, to let
>> you specify cut point by time, or by excluding some refs, or to let
>> you extend shallow boundary by commits.
>>
>> The series is now
On Thu, Feb 11, 2016 at 12:57 AM, Gary Mort wrote:
> I checked the documentation and scanned through the source code for clone:
> https://github.com/git/git/blob/master/builtin/clone.c
>
> And nothing jumps out at me as a way to specify a default depth using
> a global git configuration file. I s
On Thu, Feb 11, 2016 at 4:01 AM, Jonathan Nieder wrote:
>
>
> I really like this design. I'm tempted to implement it (since it
> lacks a bunch of the downsides of clone.bundle).
A bit disappointed we still do not address resumable fetch. But I'm
happy that it makes people excited and one of
On Thu, Feb 11, 2016 at 2:42 PM, Andrew Ardill wrote:
> On 12 February 2016 at 09:06, Junio C Hamano wrote:
>>
>> To realize this, there are low-hanging-fruit building blocks that
>> are trivial:
>>
>> - Such an annotation can be made as a note attached to the commit
>>in question;
>>
>> -
On Thu, 11 Feb 2016, Christoph Egger wrote:
+#if LIBCURL_VERSION_NUM >= 0x074400
That should probably be 0x072c00 ...
--
/ daniel.haxx.se
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vg
Add the http.pinnedpubkey configuration option for public key
pinning. It allows any string supported by libcurl --
base64(sha256(pubkey)) or filename of the full public key.
Signed-off-by: Christoph Egger
---
For some more sensitive repositories I'd like to properly pin the
public key of the
On 12 February 2016 at 09:06, Junio C Hamano wrote:
>
> To realize this, there are low-hanging-fruit building blocks that
> are trivial:
>
> - Such an annotation can be made as a note attached to the commit
>in question;
>
> - Such a check can be done in pre-commit hook;
>
> - Such a pre-co
On Thu, Feb 11, 2016 at 05:28:36PM -0500, Jeff King wrote:
> +void show_object_with_name(FILE *out, struct object *obj, const char *name)
> [...]
> fprintf(out, "%s ", oid_to_hex(&obj->oid));
> for (p = name; *p && *p != '\n'; p++)
> fputc(*p, out);
> fputc('\n', ou
On Thu, Feb 11, 2016 at 09:59:21AM -0800, Junio C Hamano wrote:
> Elia Pinto writes:
>
> > Add the FORMATPRINTF macro for declaring the gcc function attribute 'format
> > printf'
> > for code style consistency with similar macro that git already use for
> > other gcc
> > attributes. And use it
When we find a blob at "a/b/c", we currently pass this to
our show_object_fn callbacks as two components: "a/b/" and
"c". Callbacks which want the full value then call
path_name(), which concatenates the two. But this is an
inefficient interface; the path is a strbuf, and we could
simply append "c"
The "struct name_path" data is examined in only two places:
we generate it in process_tree(), and we convert it to a
single string in path_name(). Everyone else just passes it
through to those functions.
We can further note that process_tree() already keeps a
single strbuf with the leading tree pa
In the previous commit, we left name_path as a thin wrapper
around a strbuf. This patch drops it entirely. As a result,
every show_object_fn callback needs to be adjusted. However,
none of their code needs to be changed at all, because the
only use was to pass it to path_name(), which now handles
t
When "git rev-list" shows an object with its associated path
name, it does so by walking the name_path linked list and
printing each component (stopping at any embedded NULs or
newlines).
We'd like to eventually get rid of name_path entirely in
favor of a single buffer, and dropping this custom pr
The graph traversal code here passes along a name_path to
build up the pathname at which we find each blob. But we
never actually do anything with the resulting names, making
it a waste of code and memory.
This usage came in aa1dbc9 (Update http-push functionality,
2006-03-07), and originally the
The graph traversal code in list-objects.c uses "struct name_path" to
build a linked list of path components, which it then feeds to the
callbacks. This is meant to be efficient, because we keep pointers into
the actual tree data for each name. However, there are two things that
work against this:
I wish there were a way to let me annotate a commit with a statement
like this:
* When merging a branch that does not have me in it into a trunk
that already has me, do this extra check on the result of the
merge before allowing it to be recorded.
For example, suppose there is a topic that
Junio C Hamano writes:
> OK, this may answer my previous question.
>
> It might be pleasing to the eyes when these two macros appearing
> together in all CAPS, making them look similar and consistent,
> perhaps with two more tweaks:
>
> - Imitate LAST_ARG_MUST_BE_NULL and spell it FORMAT_PRINTF;
On Thu, Feb 11, 2016 at 01:32:22PM -0800, Junio C Hamano wrote:
> > ... One
> > alternative would be to amend the bundle format so that rather than a
> > single file, you get a bundle header whose end says "...and my matching
> > packfile is 1234-abcd". And then the client knows that they can fetc
Jeff King writes:
> ... One
> alternative would be to amend the bundle format so that rather than a
> single file, you get a bundle header whose end says "...and my matching
> packfile is 1234-abcd". And then the client knows that they can fetch
> that separately from the same source.
I would im
On Thu, 2016-02-11 at 11:03 +0100, Michael Haggerty wrote:
> On 02/05/2016 08:44 PM, David Turner wrote:
> > The refs infrastructure learns about log-only ref updates, which
> > only
> > update the reflog. Later, we will use this to separate symbolic
> > reference resolution from ref updating.
>
On Thu, 2016-02-11 at 09:48 +0100, Michael Haggerty wrote:
> On 02/05/2016 08:44 PM, David Turner wrote:
> > Add a database backend for refs using LMDB. This backend runs git
> > for-each-ref about 30% faster than the files backend with fully
> > -packed
> > refs on a repo with ~120k refs. It's a
On Thu, 2016-02-11 at 09:54 +0100, Michael Haggerty wrote:
> On 02/05/2016 08:44 PM, David Turner wrote:
> > Alternate refs backends might not need the refs/heads directory and
> > so
> > on, so we make ref db initialization part of the backend.
> >
> > Signed-off-by: David Turner
> > ---
> > bu
On Thu, Feb 11, 2016 at 08:03:57AM -0800, Junio C Hamano wrote:
> Michael J Gruber writes:
>
> >> Does this mean that I should warn in the release notes that some
> >> existing users might get their expectation broken but we are going
> >> ahead anyway because we think most people read left to ri
On Thu, 2016-02-11 at 10:00 +0100, Michael Haggerty wrote:
> On 02/05/2016 08:44 PM, David Turner wrote:
> > Signed-off-by: David Turner
> > ---
> > refs.c | 5 +
> > refs/files-backend.c | 4 +++-
> > refs/refs-internal.h | 9 +
> > 3 files changed, 17 insertions(+), 1
Elia Pinto writes:
> Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
> function
> attribute 'format printf'
>
> Signed-off-by: Elia Pinto
> ---
> argv-array.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/argv-array.h b/argv-array.h
> index a
On Thu, Feb 11, 2016 at 12:23 PM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Stefan Beller writes:
>>
> * This seems to clash with 00/20] refs backend.
>> Applied this on top of a merge between the current 'master' and
>> 'sb/submodule-parallel-update' topic to untangle the
Junio C Hamano writes:
> Having said that, at least for this round, I do not think there is
> nothing to do at this point on your end;...
I obviously meant "I think there is nothing" here. Sorry.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to major
Junio C Hamano writes:
> Stefan Beller writes:
>
* This seems to clash with 00/20] refs backend.
> Applied this on top of a merge between the current 'master' and
> 'sb/submodule-parallel-update' topic to untangle the dependency;
> otherwise there is no way for this topic to mak
On 11 February 2016 at 11:31, Junio C Hamano wrote:
> So it should suffice to mention it in the release notes as one
> bullet item that describes one positive change, among all other
> updates described in a simlar way. And there is no special
> "warnings for existing users" necessary, I would sa
Junio C Hamano writes:
> Stefan Beller writes:
>
>> +else {
>> +submodule->update_command = NULL;
>> +if (!strcmp(value, "none"))
>> +submodule->update = SM_UPDATE_NONE;
>> +else if (!strcmp(value
Dickson Wong writes:
> Thanks for looking into the patch.
No. Thank _you_ for contributing ;-)
> Vim buffers are not reorderable and windows are always numbered from
> top-left to bottom-right. However, I can see someone who is familiar with
> the old behavior issue a "CTRL-W_K" command to mov
Thanks for looking into the patch.
> Thanks. I, being a non-user of vim, was wondering if people who had
> their own user-defined commands (macros? and possibly short-cut keys
> to invoke them) built around the old (and odd) numbering need to
> adjust--in which case we may need to forewarn.
>
Vim
tbo...@web.de writes:
> From: Torsten Bögershausen
>
> We define the working tree file is clean if either:
>
> * the result of running convert_to_git() on the working tree
> contents matches what is in the index (because that would mean
> doing another "git add" on the path is a no-op);
On Wed, Feb 10, 2016 at 7:43 PM, Junio C Hamano wrote:
> Jonathan Nieder writes:
>
>> I really like this design. I'm tempted to implement it (since it
>> lacks a bunch of the downsides of clone.bundle).
>
> Just to see people are not stepping on each others toe, implementing
> slightly different
Elia Pinto writes:
> Add the FORMATPRINTF macro for declaring the gcc function attribute 'format
> printf'
> for code style consistency with similar macro that git already use for other
> gcc
> attributes. And use it where necessary.
>
> Elia Pinto (22):
> git-compat-util.h: add the FORMATPRI
From: Torsten Bögershausen
Factor out the code from read_cache.c retrieveing the blob, converting to
worktree format and comparing with the file on disc into convert.c.
Move static compare_with_fd() from read_cache.c to convert.c as well.
Add a shortcut in convert_cmp_checkout(): When no conve
From: Torsten Bögershausen
We define the working tree file is clean if either:
* the result of running convert_to_git() on the working tree
contents matches what is in the index (because that would mean
doing another "git add" on the path is a no-op); OR
* the result of running conv
From: Torsten Bögershausen
Whenever the size of data from convert_to_working_tree() is different
from the length of the file in the working tree, the must be different
and compare_with_fd() can be skipped.
Signed-off-by: Torsten Bögershausen
---
convert.c | 34 +
Dingyuan Wang writes:
> Hi all,
>
> I've got an assertion error when `git add .`
>
> git: pathspec.c:317: prefix_pathspec: Assertion `item->nowildcard_len <=
> item->len && item->prefix <= item->len' failed.
> Aborted (core dumped)
Sounds like http://article.gmane.org/gmane.comp.version-control.
Michael J Gruber writes:
>> Does this mean that I should warn in the release notes that some
>> existing users might get their expectation broken but we are going
>> ahead anyway because we think most people read left to right and
>> then top down? I am OK with saying that--I just wanted to make
Junio C Hamano venit, vidit, dixit 10.02.2016 18:45:
> Michael J Gruber writes:
>
>>> Second call for help. Any comments on this from anybody other than
>>> the author that I missed to support this change?
>>
>> OK, applied it (on top of next), looks sane and improves the situation
>> for the ma
Hi,
On Fri, 5 Feb 2016, Johannes Schindelin wrote:
> On Thu, 4 Feb 2016, Klinger, Xia wrote:
>
> > Thanks for confirming it. I hope a fix is available soon. I am using a
> > very old version of Git at the moment to work around this issue, which
> > doesn't comply to the requirement of our Stash
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
builtin/upload-archive.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/upload-archive.c b/builtin/upload-archive.c
index dbfe14
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
advice.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/advice.h b/advice.h
index b341a55..eef82e1 100644
--- a/advice.h
+++ b/advice.
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
builtin/receive-pack.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/builtin/receive-pack.c b/builtin/receive-pack.c
index f2d6761.
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
builtin/index-pack.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/index-pack.c b/builtin/index-pack.c
index 6a01509..5941963 1
Add the FORMATPRINTF macro for declaring the gcc function attribute 'format
printf'
for code style consistency with similar macro that git already use for other gcc
attributes.
Signed-off-by: Elia Pinto
---
git-compat-util.h | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
pkt-line.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pkt-line.h b/pkt-line.h
index 3cb9d91..d3ba3be 100644
--- a/pkt-line.h
+++
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
daemon.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/daemon.c b/daemon.c
index 46b411c..b4a9207 100644
--- a/daemon.c
+++ b/daemo
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
http-backend.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/http-backend.c b/http-backend.c
index 8870a26..c05e99f 100644
--- a/
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
strbuf.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/strbuf.h b/strbuf.h
index f72fd14..c887dab 100644
--- a/strbuf.h
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
imap-send.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/imap-send.c b/imap-send.c
index 4d3b773..6739a7c 100644
--- a/imap
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
color.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/color.h b/color.h
index e155d13..8f763d7 100644
--- a/color.h
+++ b/color.h
@
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
merge-recursive.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/merge-recursive.c b/merge-recursive.c
index 8eabde2..891d909 100644
---
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
remote.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/remote.c b/remote.c
index 35940a5..579cfcb 100644
--- a/remote.c
+++ b/remote.c
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
argv-array.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/argv-array.h b/argv-array.h
index a2fa0aa..e303dfd 100644
--- a/argv-array.h
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
transport-helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/transport-helper.c b/transport-helper.c
index a6bff8b..94c7aab 100644
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
utf8.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utf8.h b/utf8.h
index 7930b44..3dc301c 100644
--- a/utf8.h
+++ b/utf8.h
@@ -10,7 +
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
trace.h | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/trace.h b/trace.h
index 179b249..14df130 100644
--- a/trace.h
++
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
fsck.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fsck.c b/fsck.c
index c637f66..953b8e4 100644
--- a/fsck.c
+++ b/fsck.c
@@ -264,7
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
wt-status.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/wt-status.h b/wt-status.h
index c9b3b74..f8b403a 100644
--- a/wt-status.h
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
config.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.c b/config.c
index 86a5eb2..671bfd3 100644
--- a/config.c
+++ b/config.c
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
builtin/update-index.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/update-index.c b/builtin/update-index.c
index 7c5c143..cc6
Use the new FORMATPRINTF macro (in git-compat-util.h) to declare the gcc
function
attribute 'format printf'
Signed-off-by: Elia Pinto
---
cache.h | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/cache.h b/cache.h
index 553b04b..fb29154 100644
--- a/ca
Add the FORMATPRINTF macro for declaring the gcc function attribute 'format
printf'
for code style consistency with similar macro that git already use for other gcc
attributes. And use it where necessary.
Elia Pinto (22):
git-compat-util.h: add the FORMATPRINTF macro
advice.h: use the FORMATP
On 02/05/2016 08:44 PM, David Turner wrote:
> The refs infrastructure learns about log-only ref updates, which only
> update the reflog. Later, we will use this to separate symbolic
> reference resolution from ref updating.
This looks good. I assume it will get some testing later in the series.
On 02/05/2016 08:44 PM, David Turner wrote:
> Alternate refs backends might not need the refs/heads directory and so
> on, so we make ref db initialization part of the backend.
>
> Signed-off-by: David Turner
> ---
> builtin/init-db.c| 20 ++--
> refs.c | 5 +++
On 02/05/2016 08:44 PM, David Turner wrote:
> Signed-off-by: David Turner
> ---
> refs.c | 5 +
> refs/files-backend.c | 4 +++-
> refs/refs-internal.h | 9 +
> 3 files changed, 17 insertions(+), 1 deletion(-)
>
> [...]
> diff --git a/refs/refs-internal.h b/refs/refs-in
On 02/05/2016 08:44 PM, David Turner wrote:
> Add a database backend for refs using LMDB. This backend runs git
> for-each-ref about 30% faster than the files backend with fully-packed
> refs on a repo with ~120k refs. It's also about 4x faster than using
> fully-unpacked refs. In addition, and
git version 2.7.0.GIT (latest git master)
Sorry, I have found out that this problem is exactly the same as the
previous post I mentioned.
When I created the repo, scripts/ was a subrepo, and then I moved
scripts/.git out. If I add files in the scripts/ dir, SIGABRT.
在 2016年02月11日 16:24, Torsten
On 02/05/2016 08:44 PM, David Turner wrote:
> From: Ronnie Sahlberg
>
> Signed-off-by: Ronnie Sahlberg
> Signed-off-by: David Turner
> ---
> refs.c | 54
>
> refs/files-backend.c | 41 +++
>
Hi,
On Wed, Feb 10, 2016 at 10:31 AM, Matthieu Moy
wrote:
>
> So, the first question is: are there volunteers to be GSoC mentors this
> year?
I can co-mentor this year too, with you or someone else.
With you I think it will work out even if you have less time than last year.
Best,
Christian.
--
On 02/11/2016 04:59 AM, Dingyuan Wang wrote:
[]
Thanks for the bug report.
What does
git --version
give you ?
And what happens, if you run the latest version of Git ?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More ma
89 matches
Mail list logo
