[PATCH] intersect_paths: respect mode in git's tree-sort

When we do a combined diff, we individually diff against each parent, and then use intersect_paths to do a parallel walk through the sorted results and come up with a final list of interesting paths. The sort order here is that returned by the diffs, which means it is in git's tree-order which sor

Re: [PATCH 00/18] Signed push

On Tue, Aug 19, 2014 at 3:06 PM, Junio C Hamano wrote: > > If the server's GPG keychain and pre-receive hook are properly set > up, a "git push --signed" over an unauthenticated and unencrypted > communication channel (aka "git daemon") can be made as secure as, > and even more secure than, the au

Re: [PATCH 15/18] the beginning of the signed push

On Tue, Aug 19, 2014 at 03:06:24PM -0700, Junio C Hamano wrote: > While signed tags and commits assert that the objects thusly signed > came from you, who signed these objects, there is not a good way to > assert that you wanted to have a particular object at the tip of a > particular branch. My s

Re: [PATCH 00/18] Signed push

Sorry, but I cannot answer, as the only thing that I recall when I hear "branch object" was that I heard the phrase used but without much substance. I do not think I saw a clear explanation on what it is, how it is represented, how it is presented to the end user, how it is propagated across repos

Job Offer

Job Offer,$3,000 Monthly salary,For inquires & more info, contact us via email:nuamironsteelco...@outlook.com -- 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://vger.kernel.org/majordomo-info.html

Re: [PATCH] intersect_paths: respect mode in git's tree-sort

On Tue, Aug 19, 2014 at 10:14:30PM -0400, Jeff King wrote: > diff --git a/t/t4038-diff-combined.sh b/t/t4038-diff-combined.sh > index 1019d7b..71a664d 100755 > --- a/t/t4038-diff-combined.sh > +++ b/t/t4038-diff-combined.sh > @@ -401,4 +401,38 @@ test_expect_success 'combine diff missing delete bu

Re: [PATCH 00/18] Signed push

On Tue, Aug 19, 2014 at 7:54 PM, Junio C Hamano wrote: > Sorry, but I cannot answer, as the only thing that I recall when > I hear "branch object" was that I heard the phrase used but > without much substance. Just to avoid unnecessary misunderstanding, by the above, especially the "without much

Re: [PATCH 00/18] Signed push

No code == no substance might be a stretch, but definitely fair enough. I thought the idea was clear enough, but I can flesh it out if desired. The particular advantage I saw in it is that it would reuse the existing object infrastructure, and extend to branches the first-class treatment that [si

Re: [PATCH 15/18] the beginning of the signed push

On Wed, Aug 20, 2014 at 12:06 AM, Junio C Hamano wrote: > The basic flow based on this mechanism goes like this: > > 1. You push out your work with "git push -s". > > 2. The sending side learns where the remote refs are as usual, > together with what protocol extension the receiving end >

<    1   2