-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan (metze) Metzmacher wrote:
> Yes, I also think we should improve the commit mail content
> e.g. add the gitweb url, add the diff and remove some unsed stuff.
>
> But I think we can do that later
Right. So we can tweak that post migration to o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Peach schrieb:
> On Oct 5, 2007, at 9:38 AM, Gerald (Jerry) Carter wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Fyi...
>>
>> The From: on the commit mail will always be from the person
>> pushing to the repo. But the histo
On Oct 5, 2007, at 9:38 AM, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fyi...
The From: on the commit mail will always be from the person
pushing to the repo. But the history in the log commits will
be ok.
Metze, this is the standard post-receive-email script
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fyi...
The From: on the commit mail will always be from the person
pushing to the repo. But the history in the log commits will
be ok.
Metze, this is the standard post-receive-email script in
the contrib/ directory of the git source code.
jerry
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Draft Samba Repository".
The branch, v3-2-unstable has been updated
via 4da9ac14bb49c8a977b57c97402244d98aa6fb92 (commit)
via
