From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] from svn to git
Date: Tue, 18 Dec 2007 09:49:57 +0000 [thread overview]
Message-ID: <1197971300-sup-5813@tomsk> (raw)
In-Reply-To: <1197962354-sup-8779@south>
On 18.12.2007, William Morgan wrote:
> I've moved development of Sup from subversion to git. Although this is
> somewhat experimental on my part (I'm still figuring out git), I think
> it will help things in the long run. In the worst case it will be easier
> for you to maintain your own patchsets when I'm not moving fast enough
> for you. :)
Excellent - been playing with git for a while and loving it. Moving my
patchset across now!
Marcus
next prev parent reply other threads:[~2007-12-18 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 7:24 William Morgan
2007-12-18 9:36 ` Nicolas Pouillard
2007-12-18 17:40 ` William Morgan
2007-12-18 19:42 ` Nicolas Pouillard
2007-12-18 9:49 ` Marcus Williams [this message]
2007-12-18 14:40 ` Grant Hollingworth
2007-12-18 20:14 ` William Morgan
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=1197971300-sup-5813@tomsk \
--to=marcus-sup@bar-coded.net \
/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