From: Matthew Wilcox <matthew@wil.cx>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] Migrating from CVS to Git
Date: Mon, 21 Nov 2005 09:54:11 -0700 [thread overview]
Message-ID: <20051121165411.GF1598@parisc-linux.org> (raw)
I'm investigating what needs to be done to switch us from CVS to Git.
So far I've done:
- Set up a shared repository (current people with commit access:
bame,carlos,deller,grundler,jejb,kyle,rbrad,tausq,varenet,willy
others will be added on an ad-hoc basis)
- Changes made to that repository get sent to the p-l-cvs mailing list
- The repo is visible via gitweb: http://git.parisc-linux.org/
- Changes are linked from the mailing list
What needs to be converted?
- Tagging. It's now essentially free. A tag in git terms is just a
ref. You can add them at any point. So we need to figure out what
we want to bless as good.
- Autobuilding. This can change slightly as a result of how different
tagging is. Do we want to just build every time there's a commit?
It'd be a bit wasteful, but CPU and disk is cheap.
- Documentation. There's the git tutorials to link to, but something
specific to "Here's how you work on the p-l tree" would make the
learning curve less steep.
- Merging to Linus. This should hopefully be an easier process,
being easier to cherry-pick changesets out of our shared repo.
- Merging from Linus. We can now pull whenever we like, but how often
should we pull, and what bits of Linus' dev tree do we want to
inflict on our users? ;-)
I'm sure there are other things that need to be converted and discussed.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next reply other threads:[~2005-11-21 16:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 16:54 Matthew Wilcox [this message]
2005-11-21 22:25 ` [parisc-linux] Migrating from CVS to Git Grant Grundler
2005-11-22 3:16 ` Matthew Wilcox
2005-11-22 3:27 ` Kyle McMartin
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=20051121165411.GF1598@parisc-linux.org \
--to=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.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