Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] git feedback

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Jeremy Blosser <jblosser-smgl AT firinn.org>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] git feedback
  • Date: Fri, 28 Jul 2006 18:11:50 -0500

On Jul 28, seth AT swoolley.homeip.net [seth AT swoolley.homeip.net] wrote:
> Before we decide on git, the one thing I'd want is a list of things that
> _will be done_ after the decision to go forward with individual
> commitments and a timeline for when to expect those things with who will
> do them within those timeframes. This way we can enumerate the
> tractable problems and end up with a complete solution as far as we can
> predict when the process is done.

My current list of server stuff looks like:

- finish getting the p4-history git repo updated with the existing git
repo and switch to that as the live one [have methodology, working
through it]

- improve/overhaul the mail script [waiting on final decision]
- formatting: order things more usefully, add whitespace
- split things into a mail per commit when one push has multiple commits
- remove merge messages [DONE]
- get the affected paths into the subject (and the commit message if it
isn't there)
- add some headers for project/section/etc.
- if gpg keyrings change, dump the changes in a text format

- put up a git-daemon [waiting on final decision]

- clean up the other SCM trial stuff lying around fawkes [waiting on final
decision]

- get git-repack and -update-server-info running automatically [waiting on
final decision]

- get git-cvsserver running [after the repos are merged]

- integrate some of the gitweb enhancements from the xmms2 gitweb,
including:
- snapshots
- commit message bug id linking to bugzilla
- repo categorization groupings
- internal CSS refactoring

- figure out a place to publish sorcery and the grimoires via git, most
likely by getting git on ibiblio and using git:// or by uploading the
data directly and using http:// [???]


Other issues that are on lists but not necessarily mine, I'll work on these
when I'm done with the above if someone else hasn't:

- something to pull new upstream branches, eventually as a -b/-B option to
git-fetch

- better simple merging for HISTORY/ChangeLog/sometimesDETAILS/etc.

- something like a 'git-integ' script that uses git-tar-tree to emulate 'p4
integ src dst' functionality

- wiki docs


As far as timelines, stuff here keeps getting more busy instead of less,
but I still want to get the repo merging done this week(end). If we have a
final decision sometime yet this month I should be able to work through the
rest of my list during August, but it will depend on how the new baby goes.

If I find time I also want to write some kind of article to document our
trial and some of our benchmarking, a lot of people appear to be looking at
these things now and have interest in our data.

Attachment: pgpZiqGK0wOcK.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page