git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Adam Ryczkowski <adam.ryczkowski@statystyka.net>
Cc: git@vger.kernel.org
Subject: Re: Soft bug: No chance to sign synthetic commits when using git subtree External
Date: Sat, 29 Oct 2022 23:09:05 -0400	[thread overview]
Message-ID: <CAPig+cS5psokHgzV0Ri69Wi_Ba-iE9XW8uFeVybwnQuvLWomQw@mail.gmail.com> (raw)
In-Reply-To: <CAEjZQXRB47GirGP53njjGMS1gm6ydUUuxOEaj_XQGkkE8wfo5g@mail.gmail.com>

On Sat, Oct 29, 2022 at 3:32 AM Adam Ryczkowski
<adam.ryczkowski@statystyka.net> wrote:
> A week passed and my last message did not get any follow ups
> (https://lore.kernel.org/git/CAEjZQXRsMaRYrskmpn5zBCrOt3xNOZ5shoVG82kjS7A3MZQtUQ@mail.gmail.com/T/#u).
> Since it is my first post to the vger.kernel.org and I am using gmail
> (which feels awkward in the context of this list), it lets me to
> believe that the message was filtered out from human eyes somehow.
>
> I would appreciate it if someone responds to this email, just to let
> me know that the initial message was delivered successfully. Thank
> you.

Presence of your initial message in the archive is indicative that it
made it to the list itself. That nobody responded is likely due to
there being very few git-subtree users on the list rather than any
intentional lack of regard for your report. I have, myself, never used
or looked at git-subtree, hence am of no help on the subject.

      reply	other threads:[~2022-10-30  3:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  7:52 Soft bug: No chance to sign synthetic commits when using git subtree External Adam Ryczkowski
2022-10-29  7:24 ` Fwd: " Adam Ryczkowski
2022-10-30  3:09   ` Eric Sunshine [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPig+cS5psokHgzV0Ri69Wi_Ba-iE9XW8uFeVybwnQuvLWomQw@mail.gmail.com \
    --to=sunshine@sunshineco.com \
    --cc=adam.ryczkowski@statystyka.net \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).