Felipe Contreras wrote:
This is a false dichotomy; there aren't just two kinds
of Git users.
There is such a category of Git users who are not
fresh-out-of-the-boat, yet not power users either.
Oh, I didn't mean to suggest a dichotomy of any kind. However these
are the two groups (I
suggest)
Felipe Contreras felipe.contre...@gmail.com writes:
Matthieu Moy wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Commit 26cd160 (rebase -i: use a better reflog message) tried to produce
a better reflog message, however, it seems a statement was introduced by
mistake.
On Wed, Apr 23, 2014 at 03:05:42PM -0700, Junio C Hamano wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Apr 23, 2014 at 10:39:23AM -0700, Junio C Hamano wrote:
Are these three patches the same as what has been queued on
mt/patch-id-stable topic and cooking in 'next' for a few
James Denholm wrote:
Felipe Contreras wrote:
This is a false dichotomy; there aren't just two kinds
of Git users.
There is such a category of Git users who are not
fresh-out-of-the-boat, yet not power users either.
Oh, I didn't mean to suggest a dichotomy of any kind. However these
Matthieu Moy wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Matthieu Moy wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Commit 26cd160 (rebase -i: use a better reflog message) tried to produce
a better reflog message, however, it seems a statement was
Felipe Contreras felipe.contre...@gmail.com writes:
James Denholm wrote:
Felipe Contreras wrote:
This is a false dichotomy; there aren't just two kinds
of Git users.
There is such a category of Git users who are not
fresh-out-of-the-boat, yet not power users either.
Oh, I didn't
On Wed, Apr 23, 2014 at 10:44 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
diff --git a/t/t3504-cherry-pick-rerere.sh b/t/t3504-cherry-pick-rerere.sh
index e6a6481..274b2cc 100755
--- a/t/t3504-cherry-pick-rerere.sh
+++
Hello,
I installed git to my Windows 7 workstation and cloned
http://git.ipxe.org/ipxe.git; by using the Git GUI.
ipxe-23042014/src tree looks like this in Cygwin bash:
d-+ 1 peltoju Domain Users 0 Apr 23 09:00 arch
d-+ 1 peltoju Domain Users 0 Apr 23 09:00 bin
David Kastrup wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
James Denholm wrote:
Felipe Contreras wrote:
This is a false dichotomy; there aren't just two kinds
of Git users.
There is such a category of Git users who are not
fresh-out-of-the-boat, yet not power
Felipe Contreras felipe.contre...@gmail.com writes:
Recently some code was changed to do 'test_must_fail env VAR=VAL command', why
can't we do the same?
I guess we can.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line unsubscribe git in
the
Felipe Contreras felipe.contre...@gmail.com writes:
David Kastrup wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
James Denholm wrote:
Felipe Contreras wrote:
This is a false dichotomy; there aren't just two kinds
of Git users.
There is such a category of Git users
Torsten Bögershausen:
Some of the code points which have 0 length on the display are called
combining, others are called vowels or accents.
E.g. 5BF is not marked any of them, but if you look at the glyph, it should
be combining (please correct me if that is wrong).
All combining characters
Which is passed on to git diff. I very need this option instead of
changing the terminal size.
Signed-off-by: Jiri Slaby jsl...@suse.cz
---
git-request-pull.sh | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/git-request-pull.sh b/git-request-pull.sh
index
update test to match behaviour change
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
t/t4204-patch-id.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/t/t4204-patch-id.sh b/t/t4204-patch-id.sh
index cd13e8e..03f91ce 100755
--- a/t/t4204-patch-id.sh
+++
Update documentation to match behaviour change.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Documentation/git-patch-id.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-patch-id.txt b/Documentation/git-patch-id.txt
index e21b79b..9299b90
Clarify that patch ID can now be a sum of hashes, not a hash.
Document how command line and config options affect the
behaviour.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Documentation/git-patch-id.txt | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
Verify that patch ID supports an algorithm
that is stable against diff split and reordering.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
t/t4204-patch-id.sh | 128 +++-
1 file changed, 117 insertions(+), 11 deletions(-)
diff --git
Patch id changes if users
1. reorder file diffs that make up a patch
or
2. split a patch up to multiple diffs that touch the same path
(keeping hunks within a single diff ordered to make patch valid).
As the result is functionally equivalent, a different patch id is
surprising to many users.
In
API and implementation as suggested by Junio.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
t/test-lib-functions.sh | 5 +
1 file changed, 5 insertions(+)
diff --git a/t/test-lib-functions.sh b/t/test-lib-functions.sh
index aeae3ca..0e21275 100644
--- a/t/test-lib-functions.sh
+++
--stable has been the default in 'next' for a few weeks with no ill
effects.
Change the default to that so that users don't have to remember to
enable it.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
builtin/patch-id.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
I always want my diffs to show header files first,
then .c files, then the rest. Make it possible to
set orderfile though a config option to achieve this.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
diff.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/diff.c b/diff.c
index
The test is very basic and can be extended.
Couldn't find a good existing place to put it,
so created a new file.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
t/t4056-diff-order.sh | 63 +++
1 file changed, 63 insertions(+)
create mode
Am 4/24/2014 10:24, schrieb Jussi Peltonen:
I installed git to my Windows 7 workstation and cloned
http://git.ipxe.org/ipxe.git; by using the Git GUI.
ipxe-23042014/src tree looks like this in Cygwin bash:
Files have no permissions, same goes with subfolders, e.g.
$ ls -l config/
total
On Thu, Apr 24, 2014 at 12:15 AM, Jeff King p...@peff.net wrote:
I suspect the curl patch below may fix it:
diff --git a/lib/multi.c b/lib/multi.c
index bc93264..72e4825 100644
--- a/lib/multi.c
+++ b/lib/multi.c
@@ -1804,10 +1804,13 @@ static void close_all_connections(struct Curl_multi
Thanks for all suggestions and explanations.
The diff against PATCH v2 is below, PATCH v3 follows.
Have a nice day,
Stepan
Subject: [PATCH] fixup! git tag --contains : avoid stack overflow
---
t/t7004-tag.sh | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git
From: Jean-Jacques Lafay jeanjacques.la...@gmail.com
In large repos, the recursion implementation of contains(commit,
commit_list) may result in a stack overflow. Replace the recursion with
a loop to fix it.
This problem is more apparent on Windows than on Linux, where the stack
is more limited
On Thu, 24 Apr 2014, Jeff King wrote:
Thanks, that's very helpful. I wasn't able to reproduce your problem
locally, but I suspect the curl patch below may fix it:
...
Daniel, I think the similar fix to curl_multi_cleanup in commit a900d45
missed this code path, and we need something like
Fix a buffer over-stepping issue triggered by providing an absolute path
that is similar to the work tree path.
abspath_part_inside_repo() may currently increment the path pointer by
offset_1st_component() + wtlen, which is too much, since
offset_1st_component() is a subset of wtlen.
For the
On Wed, 23 Apr 2014 22:35:55 +, Felipe Contreras wrote:
...
Anyway, if you disagree change one of your frequently used passwords to a
chapter of The Lord of the Rings for a day. Let's see if you still think that.
Proving that one extreme isn't the optimum doesn't prove the other is.
On Thu, Apr 24, 2014 at 03:23:54AM -0500, Felipe Contreras wrote:
There is evidence for the claim that there won't be those problems. You have
absolutely no evidence there there will.
Felipe,
It's clear that you've not been able to produce evidence that can
convince most of the people on
Felipe Contreras felipe.contre...@gmail.com writes:
I have a branch which should always be recompiled on update;
post-update-branch would be a good place for that.
And why would pre-update-branch not serve that purpose?
Because the code that needs to be compiled is not yet in the
I don't even think we need to query the user to fill out all of the
fields. We can prepopulate a lot of the fields (name, e-mail address,
etc.) from OS specific defaults that are available on most systems ---
specifically, the default values we would use the name and e-mail
address are not
Fixed. Thanks.
On Wed, Apr 23, 2014 at 1:12 PM, Eric Sunshine sunsh...@sunshineco.com wrote:
On Tue, Apr 22, 2014 at 2:45 PM, Ronnie Sahlberg sahlb...@google.com wrote:
Change s_update_ref to use a ref transaction for the ref update.
Signed-off-by: Ronnie Sahlberg sahlb...@google.com
Michael S. Tsirkin wrote:
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -712,6 +712,11 @@ test_ln_s_add () {
fi
}
+# This function writes out its parameters, one per line
+test_write_lines () {
+ printf %s\n $@;
+}
+
Thanks for fixing this.
Nits:
* no
Hello,
I'm having problems while trying to authenticate against a TFS hosted
repository.
I experience the same problem in git for windows and in git for linux
(both versions are 1.9.2).
The problem is described on a [github msysgit/git
issue](https://github.com/msysgit/git/issues/171)
To
Michael S. Tsirkin wrote:
Documentation/git-patch-id.txt | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
Ah, there's the documentation. Please squash this with the patch that
introduces the new behavior so they can be reviewed together more
easily (both now and
Hi,
Michael S. Tsirkin wrote:
Patch id changes if users
1. reorder file diffs that make up a patch
or
2. split a patch up to multiple diffs that touch the same path
(keeping hunks within a single diff ordered to make patch valid).
As the result is functionally equivalent, a different
Jiri Slaby jsl...@suse.cz writes:
Which is passed on to git diff. I very need this option instead of
changing the terminal size.
Signed-off-by: Jiri Slaby jsl...@suse.cz
---
Interesting. I wonder if that suggests perhaps the default may be
better if it were --stat=80 regardless of your
I may have missunderstood.
So today you cannot commit if you don't provide an email address
(usually the first time you try to commit, git asks to git config
--global author.email=y...@mail.here), if I remember correctly, so
there is definitely a valid (i.e. user approved) email address.
Stefan Beller wrote:
I may have missunderstood.
So today you cannot commit if you don't provide an email address
(usually the first time you try to commit, git asks to git config
--global author.email=y...@mail.here), if I remember correctly, so
there is definitely a valid (i.e. user
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Apr 23, 2014 at 03:05:42PM -0700, Junio C Hamano wrote:
After comparing the patches 4-6 and the one that has been in 'next'
for a few weeks, I tried to like the new one, but I couldn't.
I'm fine with the one in next too.
I was under the
Stephen Leake wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
I have a branch which should always be recompiled on update;
post-update-branch would be a good place for that.
And why would pre-update-branch not serve that purpose?
Because the code that needs to be
tytso@ wrote:
On Thu, Apr 24, 2014 at 05:00:13PM +0200, Stefan Beller wrote:
I don't even think we need to query the user to fill out all of the
fields. We can prepopulate a lot of the fields (name, e-mail address,
etc.) from OS specific defaults that are available on most systems ---
Junio C Hamano gits...@pobox.com writes:
Perhaps like this?
I take that your original motivation was to confirm to run a tool on
this particular (as opposed to another) path, but the user can also
take the prompt as to confirm to run this (as opposed to some other)
tool. The latter of
Jonathan Nieder jrnie...@gmail.com writes:
Michael S. Tsirkin wrote:
--- a/t/test-lib-functions.sh
+++ b/t/test-lib-functions.sh
@@ -712,6 +712,11 @@ test_ln_s_add () {
fi
}
+# This function writes out its parameters, one per line
+test_write_lines () {
+printf %s\n $@;
+}
Stefan Beller wrote:
I may have missunderstood.
So today you cannot commit if you don't provide an email address
(usually the first time you try to commit, git asks to git config
--global author.email=y...@mail.here), if I remember correctly, so
there is definitely a valid (i.e. user
Jonathan Nieder wrote:
Stefan Beller wrote:
I may have missunderstood.
So today you cannot commit if you don't provide an email address
(usually the first time you try to commit, git asks to git config
--global author.email=y...@mail.here), if I remember correctly, so
there is
Martin Erik Werner martinerikwer...@gmail.com writes:
Fix a buffer over-stepping issue triggered by providing an absolute path
that is similar to the work tree path.
abspath_part_inside_repo() may currently increment the path pointer by
offset_1st_component() + wtlen, which is too much,
David Kastrup wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
David Kastrup wrote:
The people having to read and understand scripts written in the
expectation of default aliases.
Which are imaginary.
And I prefer them to stay that way since then one does not need to worry
Hi,
On Apr 22, 2014 2:53 AM, Junio C Hamano gits...@pobox.com wrote:
Richard Hansen rhan...@bbn.com writes:
Both bash and zsh subject the value of PS1 to parameter expansion,
command substitution, and arithmetic expansion. Rather than include
the raw, unescaped branch name in PS1
Andreas Krey wrote:
On Wed, 23 Apr 2014 22:35:55 +, Felipe Contreras wrote:
...
Anyway, if you disagree change one of your frequently used passwords to a
chapter of The Lord of the Rings for a day. Let's see if you still think
that.
Proving that one extreme isn't the optimum doesn't
Michael S. Tsirkin m...@redhat.com writes:
The test is very basic and can be extended.
Couldn't find a good existing place to put it,
so created a new file.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
t/t4056-diff-order.sh | 63
Theodore Ts'o wrote:
On Thu, Apr 24, 2014 at 03:23:54AM -0500, Felipe Contreras wrote:
There is evidence for the claim that there won't be those problems. You have
absolutely no evidence there there will.
It's clear that you've not been able to produce evidence that can
convince most
David Kastrup d...@gnu.org writes:
d...@mailtor.net writes:
It would be nice if we could change the flags to either
a) avoid cutting off
b) indicate something has been cut off (- I prefer this)
I assume there are more people with a similar workflow who're still
unaware of this feature.
Jonathan Nieder jrnie...@gmail.com writes:
Should the internal patch-id computation used by commands like 'git
cherry' (see diff.c::diff_get_patch_id) get the same change? (Not a
rhetorical question --- I don't know what the right choice would be
there.)
I thought about it but I did not
On Thu, Apr 24, 2014 at 01:26:33PM -0500, Felipe Contreras wrote:
Jonathan Nieder wrote:
Stefan Beller wrote:
I may have missunderstood.
So today you cannot commit if you don't provide an email address
(usually the first time you try to commit, git asks to git config
--global
On Thu, 24 Apr 2014, Felipe Contreras wrote:
David Kastrup wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
David Kastrup wrote:
The people having to read and understand scripts written in the
expectation of default aliases.
Which are imaginary.
And I prefer them to stay that
Felipe Contreras felipe.contre...@gmail.com writes:
Andreas Krey wrote:
On Wed, 23 Apr 2014 22:35:55 +, Felipe Contreras wrote:
...
Anyway, if you disagree change one of your frequently used passwords to a
chapter of The Lord of the Rings for a day. Let's see if you still think
that.
Junio C Hamano gits...@pobox.com writes:
Traditionally, because the tool grew in a context of being used in a
project whose participants are at least not malicious, always having
to be on the lookout for fear of middle-of-line tabs hiding bad
contents near the right edges of lines has never
David Kastrup d...@gnu.org writes:
Junio C Hamano gits...@pobox.com writes:
Traditionally, because the tool grew in a context of being used in a
project whose participants are at least not malicious, always having
to be on the lookout for fear of middle-of-line tabs hiding bad
contents near
Allow ignoring submodules (or not) by command line switch, like diff
and status do.
This commit is also a prerequisite for the next one in series, which
adds the --ignore-submodules switch to git commit. That's why a new
argument is added to public function add_files_to_cache(), and its
call
Allow ignoring submodules (or not) by command line switch, like diff
and status do.
Git commit honors the 'ignore' setting from .gitmodules or .git/config,
but didn't allow to override it from command line.
This patch depends on Jens Lehmann's patch commit -m: commit staged
submodules regardless
On Thu, Apr 24, 2014 at 09:41:06AM -0400, Theodore Ts'o wrote:
On Thu, Apr 24, 2014 at 03:23:54AM -0500, Felipe Contreras wrote:
Creating a ~/.gitconfig file if one doesn't already is one I agree
with, and at least on Unix systems, telling them that the config file
lives in ~/.gitconfig, or
On Thu, Apr 24, 2014 at 10:33:25AM -0700, Jonathan Nieder wrote:
Michael S. Tsirkin wrote:
Documentation/git-patch-id.txt | 23 ++-
1 file changed, 18 insertions(+), 5 deletions(-)
Ah, there's the documentation. Please squash this with the patch that
introduces the
On Thu, Apr 24, 2014 at 10:30:44AM -0700, Jonathan Nieder wrote:
Hi,
Michael S. Tsirkin wrote:
Patch id changes if users
1. reorder file diffs that make up a patch
or
2. split a patch up to multiple diffs that touch the same path
(keeping hunks within a single diff ordered to make
On Thu, Apr 24, 2014 at 12:29:21PM -0700, Junio C Hamano wrote:
David Kastrup d...@gnu.org writes:
Junio C Hamano gits...@pobox.com writes:
Traditionally, because the tool grew in a context of being used in a
project whose participants are at least not malicious, always having
to be
On Thu, Apr 24, 2014 at 11:45:35AM -0700, Junio C Hamano wrote:
Michael S. Tsirkin m...@redhat.com writes:
The test is very basic and can be extended.
Couldn't find a good existing place to put it,
so created a new file.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
Jeff King p...@peff.net writes:
I would think it's the opposite. Long lines look _horrible_ without
-S, as they get wrapped at awkward points. Using -S means that long
lines don't bug you, unless you really want to scroll over and see the
content.
I really think the right solution here is
On Thu, Apr 24, 2014 at 02:47:01PM -0700, Junio C Hamano wrote:
And I do agree that the chopped marker would be a very sensible
thing to show in the -S output; I would have chosen $ myself for
that to match an existing practice in (setq truncate-lines t) in
Emacs, though.
Hmm. I do not use
Jeff King p...@peff.net writes:
On Thu, Apr 24, 2014 at 12:29:21PM -0700, Junio C Hamano wrote:
David Kastrup d...@gnu.org writes:
Junio C Hamano gits...@pobox.com writes:
Traditionally, because the tool grew in a context of being used in a
project whose participants are at least not
On Thu, Apr 24, 2014 at 11:48:30PM +0200, David Kastrup wrote:
I really think the right solution here is to teach less to make it more
obvious that there is something worth scrolling over to. Here's a very
rough patch for less, if you want to see what I'm thinking of.
Still useless. I'm
Michael S. Tsirkin m...@redhat.com writes:
+--unstable::
+ Use a non-symmetrical sum of hashes, such that reordering
What is a non-symmetrical sum?
Non-symmetrical combination function is better?
I do not think either is very good X-.
The primary points to convey for --stable are:
-
Jeff King p...@peff.net writes:
On Thu, Apr 24, 2014 at 11:48:30PM +0200, David Kastrup wrote:
I really think the right solution here is to teach less to make it more
obvious that there is something worth scrolling over to. Here's a very
rough patch for less, if you want to see what I'm
Felipe Contreras wrote:
@@ -635,9 +637,10 @@ static int do_pick_commit(struct commit *commit, struct
replay_opts *opts)
}
if (opts-skip_empty is_index_unchanged() == 1) {
- warning(_(skipping %s... %s),
-
Felipe Contreras wrote:
Akin to 'am --skip' and 'rebase --skip'.
I don't recall why my original sequencer series didn't include this
option. Perhaps Jonathan remembers?
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More
Felipe Contreras wrote:
So that we can load and store rewrites, as well as other operations on a
list of rewritten commits.
Please elaborate. Explain why this code shouldn't go in sequencer.c.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
Felipe Contreras wrote:
If no action-name is specified, nothing is done.
Why? Is it because git-rebase implements its own notes-copy-on-rewrite logic?
Otherwise, I agree with the goal of making notes.rewrite.command
work for cherry-pick.
--
To unsubscribe from this list: send the line
Felipe Contreras wrote:
diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
index 43631b4..fd085e1 100644
--- a/git-rebase--interactive.sh
+++ b/git-rebase--interactive.sh
@@ -248,7 +248,7 @@ pick_one () {
test -d $rewritten
Hi,
David Kastrup wrote:
Jeff King p...@peff.net writes:
There are two questions here:
1. Can less do a better job of indicating what's in the input when -S
is in effect?
2. What should get put into $LESS by default?
I was specifically addressing (1). Your comment does not help
Ramkumar Ramachandra wrote:
Felipe Contreras wrote:
@@ -635,9 +637,10 @@ static int do_pick_commit(struct commit *commit,
struct replay_opts *opts)
}
if (opts-skip_empty is_index_unchanged() == 1) {
- warning(_(skipping %s... %s),
-
Ramkumar Ramachandra wrote:
Felipe Contreras wrote:
So that we can load and store rewrites, as well as other operations on a
list of rewritten commits.
Please elaborate. Explain why this code shouldn't go in sequencer.c.
Isn't it obvious? Because sequencer.c wouldn't be the only user.
--
Ramkumar Ramachandra wrote:
Felipe Contreras wrote:
If no action-name is specified, nothing is done.
Why? Is it because git-rebase implements its own notes-copy-on-rewrite logic?
Yes, and `git rebase` uses `git cherry-pick`.
--
Felipe Contreras
--
To unsubscribe from this list: send the
Ramkumar Ramachandra wrote:
Felipe Contreras wrote:
diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh
index 43631b4..fd085e1 100644
--- a/git-rebase--interactive.sh
+++ b/git-rebase--interactive.sh
@@ -248,7 +248,7 @@ pick_one () {
test -d $rewritten
Felipe's
===
= The publish tracking branch =
I still have problems getting upstream branches correctly configured
as to have this introduced, anyway, I suppose it's optional, so
nothing to add on that.
By the way, remote branch managing has improved a lot, one of the
best things I see for
Javier Domingo Cansino wrote:
Felipe's
===
= The publish tracking branch =
I still have problems getting upstream branches correctly configured
as to have this introduced, anyway, I suppose it's optional, so
nothing to add on that.
I did so too, until I patch `git branch -v` to be
When applying binary patches a full index is required. format-patch
already handles this, but diff-tree needs '--full-index' argument
to always output full index.
Signed-off-by: Tolga Ceylan tolga.cey...@gmail.com
---
git-p4.py |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Sat, Apr 19, 2014 at 12:43 AM, Junio C Hamano gits...@pobox.com wrote:
Having said that, I do not think there is a fundamental reason why
the stat data has to live inside the same index file. A separate
file is just fine, as long as you can reliably detect that they went
out of sync for
On Thu, Apr 24, 2014 at 02:24:39PM +0200, Stepan Kasal wrote:
From: Jean-Jacques Lafay jeanjacques.la...@gmail.com
In large repos, the recursion implementation of contains(commit,
commit_list) may result in a stack overflow. Replace the recursion with
a loop to fix it.
This problem is
88 matches
Mail list logo
