Michael J Gruber writes:
> Junio C Hamano venit, vidit, dixit 16.06.2016 19:06:
>
>> I am not so imaginative, either. One remotely plausible use case may
>> be a project that has two classes of paths (let's call these classes
>> sensitive and others), and requires its
Junio C Hamano venit, vidit, dixit 16.06.2016 19:06:
> Jeff King writes:
>
>> But why does somebody run "commit -S" for a single commit, but not all
>> the time? Is it because that commit is special? Or is that particular
>> moment special? One implies that it's important for the
Jeff King writes:
> But why does somebody run "commit -S" for a single commit, but not all
> the time? Is it because that commit is special? Or is that particular
> moment special? One implies that it's important for the signature to be
> retained during a rebase, and one does
On Wed, Jun 15, 2016 at 09:07:16AM +0200, Michael J Gruber wrote:
> > Ah, so the problem is probably that you had a signature _initially_, but
> > that it did not survive the rebase. Which makes sense, as rebase would
> > need to re-sign. It does not by default, but you can tell it to do so
> >
Thank you all very much!
-Schrödinger
On Wed, Jun 15, 2016 at 3:07 PM, Michael J Gruber
wrote:
> Jeff King venit, vidit, dixit 15.06.2016 06:34:
>> On Wed, Jun 15, 2016 at 12:27:15PM +0800, ZhenTian wrote:
>>
>>> I got two more lines from gpg -v during commit with -S:
Jeff King venit, vidit, dixit 15.06.2016 06:34:
> On Wed, Jun 15, 2016 at 12:27:15PM +0800, ZhenTian wrote:
>
>> I got two more lines from gpg -v during commit with -S:
>> ```
>> gpg: writing to stdout
>> gpg: RSA/SHA1 signature from: "2EF2AD6E Tian Zhen "
>> ```
>>
>>
On Wed, Jun 15, 2016 at 12:27:15PM +0800, ZhenTian wrote:
> I got two more lines from gpg -v during commit with -S:
> ```
> gpg: writing to stdout
> gpg: RSA/SHA1 signature from: "2EF2AD6E Tian Zhen "
> ```
>
> after I commit, I push it to remote, but someone had pushed
Hi Michael and Peff,
I got two more lines from gpg -v during commit with -S:
```
gpg: writing to stdout
gpg: RSA/SHA1 signature from: "2EF2AD6E Tian Zhen "
```
after I commit, I push it to remote, but someone had pushed before to
master branch, so I pull on master
On Tue, Jun 14, 2016 at 04:39:38PM +0800, ZhenTian wrote:
> I want to set gpg -v to pgp.program, but if I set it, it can't call gpg:
> ```
> error: cannot run gpg -v: No such file or directory
> error: could not run gpg.
> fatal: failed to write commit object
> ```
>
> I have tried set
Hi Peff,
I want to set gpg -v to pgp.program, but if I set it, it can't call gpg:
```
error: cannot run gpg -v: No such file or directory
error: could not run gpg.
fatal: failed to write commit object
```
I have tried set gpg.program value to `gpg|/tmp/log`, `/usr/bin/gpg
-v`, `gpg -v`,
On Tue, Jun 14, 2016 at 04:09:52PM +0800, ZhenTian wrote:
> I have tested sign my work in another project, it works fine, I have
> committed five times, all commits are signed.
>
> I can't find encoded signature block in the output of "git cat-file
> commit HEAD", only these:
> ```
> tree
Hi Peff,
I commit via this command: gcs -nm "feat: mobile support free freight
hint, closed #1417"
gcs is an alias in zsh, which is: git commit -S
I have tested sign my work in another project, it works fine, I have
committed five times, all commits are signed.
I can't find encoded signature
On Tue, Jun 14, 2016 at 03:50:43PM +0800, ZhenTian wrote:
> I commit with -S argument, and I got some output like this:
>
> You need a passphrase to unlock the secret key for
> user: "Tian Zhen "
> 4096-bit RSA key, ID 2EF2AD6E, created 2016-05-21
>
> [master d107770]
Hi git developers,
I commit with -S argument, and I got some output like this:
You need a passphrase to unlock the secret key for
user: "Tian Zhen "
4096-bit RSA key, ID 2EF2AD6E, created 2016-05-21
[master d107770] feat: mobile support free freight hint, closed #1417
14 matches
Mail list logo