From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Noel Ullreich <n.ullreich@proxmox.com>
Cc: Noel Ullreich <nullreich@eloa.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/5] readme: fixed typo in readme
Date: Thu, 24 Nov 2022 10:09:26 +0100 [thread overview]
Message-ID: <b2003acc-d759-b8d9-2d2f-ce1dd95a13a1@proxmox.com> (raw)
In-Reply-To: <20221123174810.2703466-2-n.ullreich@proxmox.com>
Am 23/11/2022 um 18:48 schrieb Noel Ullreich:
> From: Noel Ullreich <nullreich@eloa.proxmox.com>
erm, fix your git config I guess?
https://pve.proxmox.com/wiki/Developer_Documentation#Using_git
-> git config --global user.email 'n.ullreich@proxmox.com'
You can then rebase the series interactively, stopping on each commit
and use `git commit --amend --reset-author` to fix-up the author to the
currently configured, now hopefully correct, name+mail.
next prev parent reply other threads:[~2022-11-24 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:48 [pbs-devel] [PATCH proxmox-backup 0/5] added section on ransomware to docs Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 1/5] readme: fixed typo in readme Noel Ullreich
2022-11-24 9:09 ` Thomas Lamprecht [this message]
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 2/5] docs: changed wording Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 3/5] docs: fixed capitalization Noel Ullreich
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 4/5] docs: main features ransomware Noel Ullreich
2022-11-24 9:35 ` Thomas Lamprecht
2022-11-23 17:48 ` [pbs-devel] [PATCH proxmox-backup 5/5] docs: added section on ransomware Noel Ullreich
2022-11-24 10:23 ` Thomas Lamprecht
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=b2003acc-d759-b8d9-2d2f-ce1dd95a13a1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=n.ullreich@proxmox.com \
--cc=nullreich@eloa.proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.