Re: [PATCH] Added get sendmail from .mailrc

2014-01-25 Thread Brilliantov Kirill Vladimirovich
On 2014-01-25 22:37:21, Eric Wong wrote: > Brilliantov Kirill Vladimirovich wrote: > > Signed-off-by: Brilliantov Kirill Vladimirovich > > --- > > git-send-email.perl | 18 ++ > > 1 file changed, 18 insertions(+) > > Some documentation references to .mailrc and its format would

Re: [PATCH] tree_entry_interesting: match against all pathspecs

2014-01-25 Thread Duy Nguyen
On Sat, Jan 25, 2014 at 10:06:46PM +, Andy Spencer wrote: > The current basedir compare aborts early in order to avoid futile > recursive searches. However, a match may still be found by another > pathspec. This can cause an error while checking out files from a branch > when using multiple pat

Re: [PATCH] Added get sendmail from .mailrc

2014-01-25 Thread Eric Wong
Brilliantov Kirill Vladimirovich wrote: > Signed-off-by: Brilliantov Kirill Vladimirovich > --- > git-send-email.perl | 18 ++ > 1 file changed, 18 insertions(+) Some documentation references to .mailrc and its format would be nice. > --- a/git-send-email.perl > +++ b/git-send-

[PATCH] tree_entry_interesting: match against all pathspecs

2014-01-25 Thread Andy Spencer
The current basedir compare aborts early in order to avoid futile recursive searches. However, a match may still be found by another pathspec. This can cause an error while checking out files from a branch when using multiple pathspecs: $ git checkout master -- 'a/*.txt' 'b/*.txt' error: pathspec

Re: Verifiable git archives?

2014-01-25 Thread Andy Lutomirski
Here's a rather hackish implementation of the write side. Any thoughts on the format? (Obviously the implementation needs work. For example, it needs to be optional. Thoughts so far: - I want to put the value of "prefix" into an extended header. - Should blobs have their sha1 hashes in an exte

Re: Globbing for ignored branches?

2014-01-25 Thread Jeff King
On Sat, Jan 25, 2014 at 03:15:42PM +0100, Markus Trippelsdorf wrote: > Many thanks for the patch. It seems to work as advertised, but only if > the negative refspec appears on a separate line. For example: > > [remote "origin"] > url = git://gcc.gnu.org/git/gcc.git > fetch = +refs

[PATCH 1/3] builtin/blame.c: struct blame_entry does not need a prev link

2014-01-25 Thread David Kastrup
Signed-off-by: David Kastrup --- builtin/blame.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/builtin/blame.c b/builtin/blame.c index e44a6bb..2195595 100644 --- a/builtin/blame.c +++ b/builtin/blame.c @@ -197,7 +197,6 @@ static void drop_origin_blob(struct o

[PATCH 0/3] "Teaser" patch for rewriting blame for efficiency

2014-01-25 Thread David Kastrup
Ok, here is the "teaser" for the git-blame rewrite. The first two patches are already in pu and only contained for simplicity. The third patch gives a pretty good idea about the work that's up. It is missing support for the -M and -C options (I think, if that's what the "move" and "copy" detecti

[PATCH 2/3] Eliminate same_suspect function in builtin/blame.c

2014-01-25 Thread David Kastrup
Since the origin pointers are "interned" and reference-counted, comparing the pointers rather than the content is enough. The only uninterned origins are cached values kept in commit->util, but same_suspect is not called on them. Signed-off-by: David Kastrup --- builtin/blame.c | 25 ---

[PATCH 3/3] builtin/blame.c: large-scale rewrite

2014-01-25 Thread David Kastrup
The previous implementation uses a sorted linear list of struct blame_entry in a struct scoreboard for organizing all partial or completed work. Every task that is done requires going through the whole list where most entries are not relevant to the task at hand. This commit reorganizes the data

Re: Globbing for ignored branches?

2014-01-25 Thread Markus Trippelsdorf
On 2014.01.25 at 15:15 +0100, Markus Trippelsdorf wrote: > On 2014.01.24 at 20:34 -0500, Jeff King wrote: > > On Fri, Jan 24, 2014 at 01:08:42PM -0800, Junio C Hamano wrote: > > > > > Not really. You do not have to view it as "'not refs/heads/foo' is > > > affecting the previous '+refs/heads/*:re

Re: Globbing for ignored branches?

2014-01-25 Thread Markus Trippelsdorf
On 2014.01.24 at 20:34 -0500, Jeff King wrote: > On Fri, Jan 24, 2014 at 01:08:42PM -0800, Junio C Hamano wrote: > > > Not really. You do not have to view it as "'not refs/heads/foo' is > > affecting the previous '+refs/heads/*:refs/remotes/origin/*'". > > > > You can think of two refspecs "refs

[PATCH] Makefile: remove redundant object in git-http{fetch,push}

2014-01-25 Thread John Keeping
revision.o is included in libgit.a which is in $(GITLIBS), so we don't need to include is separately. This fixes compilation with "-fwhole-program" which otherwise fails with messages like this: libgit.a(revision.o): In function `mark_tree_uninteresting': /home/john/src/git/revision.c:108: mu

How to substructure rewrites?

2014-01-25 Thread David Kastrup
Hi, I'm currently rewriting the internals of git-blame. For the somewhat academic example #/bin/sh cd /tmp rm -rf testit mkdir testit cd testit git init for inc in 8 4 3 7 2 9 5 6 1 do seq 252000 -$inc 0 > testfile git add testfile git commit -m "Run with increment $inc" done time

[PATCH] Added get sendmail from .mailrc

2014-01-25 Thread Brilliantov Kirill Vladimirovich
Signed-off-by: Brilliantov Kirill Vladimirovich --- git-send-email.perl | 18 ++ 1 file changed, 18 insertions(+) diff --git a/git-send-email.perl b/git-send-email.perl index 2016d9c..5345fdb 100755 --- a/git-send-email.perl +++ b/git-send-email.perl @@ -28,6 +28,7 @@ use File::T