From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>
Cc: dwz@sourceware.org, jakub@redhat.com
Subject: Re: [PATCH] Release process improvements
Date: Sun, 28 Mar 2021 10:21:28 +0200 [thread overview]
Message-ID: <d29f5ee1-c8de-6aec-f3e7-b7c85cb03263@suse.de> (raw)
In-Reply-To: <20210327225435.GP2685@wildebeest.org>
On 3/27/21 11:54 PM, Mark Wielaard wrote:
> Hi Tom,
>
> On Fri, Mar 12, 2021 at 10:05:53AM +0100, Tom de Vries wrote:
>> That email also contains a suggestion on how to move things to git,
>> which might be a nice improvement. [ I don't really understand how to
>> go about that, maybe you understand the suggestion better? Anyway,
>> otherwise, we can ask for clarifications. ]
>
> It took me a while, but I now understand how to transform the CVS repo
> into a git repo. Which I just did. So now we can update our webpages
> through https://sourceware.org/git/dwz-htdocs.git
>
Thanks Mark, that's awesome :)
Cheers,
- Tom
prev parent reply other threads:[~2021-03-28 8:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:13 Tom de Vries
2021-03-11 15:32 ` Mark Wielaard
2021-03-12 9:05 ` Tom de Vries
2021-03-27 22:54 ` Mark Wielaard
2021-03-28 8:21 ` Tom de Vries [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d29f5ee1-c8de-6aec-f3e7-b7c85cb03263@suse.de \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=mark@klomp.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.
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).