Front page | perl.perl5.porters |
Postings from March 2008
Re: Switching to Git
Thread Previous
|
Thread Next
From:
Rafael Garcia-Suarez
Date:
March 6, 2008 08:37
Subject:
Re: Switching to Git
Message ID:
b77c1dce0803060837u7fa40cfbw6422c2516a47a560@mail.gmail.com
On 06/03/2008, John Peacock <john.peacock@havurah-software.org> wrote:
> Rafael Garcia-Suarez wrote:
> > * public repository cloneable via git protocol (optionally http protocol too)
> > * writable via ssh
> > * browseable on-line via gitweb
> > * maybe a cvs interface (readonly) via git-cvsserver ? I'm thinking
> > about the VMS people here mostly. Or would rsync be better ?
> > * interfacing the commits to the major branches to perl5-changes@.
>
>
> I'd really like a R/W git-svnserver be available as well. You also
> haven't described a formal backup mechanism (rather than just relying on
> everyone's mirrors to rebuild).
Backup is part of hosting. More on that later :)
> We also desperately need specific documentation:
>
> * Mapping between Perforce commands and the equivalent git command (for
> the few of us who at least sometimes use Perforce);
git is a distributed VCS; Perforce isn't. There's no one to one mapping...
> * Perl centric git cheat sheet for common operations (like update to
> change #12345) for the casual user (1).
... however I mentioned in another mail it would be great to have a day-to-day
guide at hacking perl with git for dummies. Something in a few list of basic
commands:
- clone (what, how)
- branch (to start hacking)
- commit (to continue hacking)
- fetch / merge / pull / rebase (to update your copy and your branches)
- format-patch (to send patches to P5P)
- where is the repository browser
But some clarifications on the workflow and the hosting must be done first.
Thread Previous
|
Thread Next