From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Dodji Seketeli <dodji@seketeli.org>
Subject: Re: Request for moving libabigail's web from CVS to Git
Date: Mon, 3 Oct 2022 10:48:30 -0400 [thread overview]
Message-ID: <20221003144830.GK7916@redhat.com> (raw)
In-Reply-To: <86v8p15m3o.fsf@seketeli.org>
Hi -
> At the moment, the web pages of the libabigail project are maintained
> using the venerable CVS at sourceware.org/cvs/libabigail.
> It would be wonderful if those web pages could rather be maintained in
> git.
> Do you think that would be possible?
All done, including import of CVS history.
Pushing to /git/libabigail-htdocs.git should autoupdate your web pages.
For next time, steps outlined here:
https://sourceware.org/sourceware-wiki/OSNewWebHosting/?updated
- FChE
prev parent reply other threads:[~2022-10-03 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 8:48 Dodji Seketeli
2022-10-03 14:48 ` Frank Ch. Eigler [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=20221003144830.GK7916@redhat.com \
--to=fche@redhat.com \
--cc=dodji@seketeli.org \
--cc=overseers@sourceware.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).