From: Junio C Hamano <gitster@pobox.com>
To: Stefan Moch <stefanmoch@mail.de>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
dwh@linuxprogrammer.org, git <git@vger.kernel.org>
Subject: Re: Preserving the ability to have both SHA1 and SHA256 signatures
Date: Sat, 08 May 2021 20:12:02 +0900 [thread overview]
Message-ID: <xmqqlf8ptr7h.fsf@gitster.g> (raw)
In-Reply-To: <f4f782c4-3adc-8c1c-428d-8037426fc475@mail.de> (Stefan Moch's message of "Sat, 8 May 2021 12:11:51 +0200")
Stefan Moch <stefanmoch@mail.de> writes:
> Good idea to write this down. How to use the mailing list is only
> sparsely documented. The following files talk about sending to the
> mailing list:
>
> 1. README.md
> 2. Documentation/SubmittingPatches
> 3. Documentation/MyFirstContribution.txt
> 4. MaintNotes (in Junio's “todo” branch, sent out to the list from
> time to time as “A note from the maintainer”)
>
> 2, 3 and 4 mention sending Cc to everyone involved.
>
> 2 is about new messages.
>
> 3 and 4 specifically talk about keeping everyone in Cc: in replies.
> Both in the context of “you don't have to be subscribed and you
> don't need to ask for Cc:”.
In case somebody wants to write a doc, a better pair of references
than what I quoted earlier to draw material from are:
https://public-inbox.org/git/7v4pndfjym.fsf@assigned-by-dhcp.cox.net/
https://public-inbox.org/git/7vei7zjr3y.fsf@alter.siamese.dyndns.org/
next prev parent reply other threads:[~2021-05-08 11:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 2:22 Preserving the ability to have both SHA1 and SHA256 signatures dwh
2021-05-08 6:39 ` Christian Couder
2021-05-08 6:56 ` Junio C Hamano
2021-05-08 8:03 ` Felipe Contreras
2021-05-08 10:11 ` Stefan Moch
2021-05-08 11:12 ` Junio C Hamano [this message]
2021-05-09 0:19 ` brian m. carlson
2021-05-10 12:22 ` Is the sha256 object format experimental or not? Ævar Arnfjörð Bjarmason
2021-05-10 22:42 ` brian m. carlson
2021-05-13 20:29 ` dwh
2021-05-13 20:49 ` Konstantin Ryabitsev
2021-05-13 23:47 ` dwh
2021-05-14 13:45 ` Konstantin Ryabitsev
2021-05-14 17:39 ` dwh
2021-05-13 21:03 ` Junio C Hamano
2021-05-13 23:26 ` dwh
2021-05-14 8:49 ` Ævar Arnfjörð Bjarmason
2021-05-14 18:10 ` dwh
2021-05-18 5:32 ` Jonathan Nieder
2021-05-16 20:57 Preserving the ability to have both SHA1 and SHA256 signatures Personal Sam Smith
2021-05-17 3:23 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlf8ptr7h.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=dwh@linuxprogrammer.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=stefanmoch@mail.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).