Bert Wesarg writes:
> 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 ex
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
>
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
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 signing v2.0.1 tag only means I want to call
the version v2.0.1, and it d
4 matches
Mail list logo