From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: Nigel Cunningham <ncunningham@linuxmail.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Place for userland swsusp parts
Date: Fri, 13 Jan 2006 12:25:51 +0100 [thread overview]
Message-ID: <200601131225.51635.rjw@sisk.pl> (raw)
In-Reply-To: <20060113002138.GE10088@elf.ucw.cz>
Hi,
On Friday, 13 January 2006 01:21, Pavel Machek wrote:
> > > > On Thursday 12 January 2006 08:15, Pavel Machek wrote:
> > > > > Is there some place where we could put userland swsusp parts under
> > > > > version control?
> > > > >
> > > > > swsusp.sf.net looks like possible place, but it has been in use by
> > > > > suspend2... Is it still being used? If not, would it be possible to
> > > > > "hijack" it for swsusp development?
> > > >
> > > > It's not still being used (we have suspend2.net now). The only problem I see
> > > > with that is that it still has all the old suspend2 stuff and Sourceforge
> > > > make it really hard to clear out a project's files. You were talking about
> > > > calling it uswsusp or something like that. How about starting a
> > > > uswsusp.sf.net?
> > >
> > > Rafael, do you have repository to place userland parts in, or should I
> > > start uswsusp.sf.net project, or do you want to do it?
> >
> > I think I can host them (the box is moving tomorrow, hopefully, so it should get
> > enough bandwidth ;-)), but I'm afraid I won't have time to set up a mailing list
> > etc.
>
> Actually, it would probably be better to put it on sourceforge or
> something like that. That way you don't have to care about sysadmin
> stuff (mailing lists etc), backups, backup conectivity, etc, etc.
Agreed.
> > IMHO uswsusp.sf.net would be too similar to swsusp.sf.net, especially that
> > swsusp.sf.net is redirected to www.suspend2.net.
>
> Or maybe we can get hosting on suspend2.net? Or create
> userswsusp.sf.net (that name is ugly :-().
suspend.sf.net seems to be available. We can use it, I think.
> ...some revision control would be nice, but perhaps revision control
> is enough and we can just put git tree on kernel.org?
IMHO quilt will suffice to manage patches, at least for starters, but we'll
need a mailing list and an intro web page.
Greetings,
Rafael
next prev parent reply other threads:[~2006-01-13 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 22:15 Place for userland swsusp parts Pavel Machek
2006-01-11 22:19 ` Nigel Cunningham
2006-01-12 14:38 ` Pavel Machek
2006-01-12 20:13 ` Rafael J. Wysocki
2006-01-13 0:21 ` Pavel Machek
2006-01-13 1:00 ` Bernard Blackham
2006-01-13 11:25 ` Rafael J. Wysocki [this message]
2006-01-13 12:09 ` Pavel Machek
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=200601131225.51635.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@suse.cz \
/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