Those tars weren't in the original phpMp repository, were they?  As Max
said, it'd be best to start from that (preserve the history).  If they
really were in the original one, you could use git filter-branch to alter
the history (but this is scary!).

As for the multiple clients thing...  it doesn't make much sense to me to
have multiple projects in a single repository.  If there's something to be
gained from each of these clients, the right approach would be to add the
features from all the rest to phpMp (if they're mutually exclusive, allow
configuration).  We don't want a handful of choices which between them
provide all the features, we want one single great web client.

Jeffrey

On Sun, Feb 28, 2010 at 9:18 AM, Sven Ginka <sven.gi...@gmail.com> wrote:

> Hi,
>
> As you can clearely see I am new to git and its use :-). Yes thats true
> there were
> the original tars in it first so the repo exploded to 48mb. As soon as I
> figured out
> how to bann them from the history the repo will be a couple of kbs.
>
> @stefan
> there are heaps of mpd-webclients out there. I downloaded most of them
> and tried
> each to figure out which one suits to my needs. mostly there were no
> changes since
> years on some clients. I thought it would be nice to simply download a
> package
> of webclients where I could simply switch to any client -- this is going
> to be phpMpReloaded.
>
> best
> -tswaehn
>
>
> Max Kellermann wrote:
> > On 2010/02/26 10:36, Sven Ginka <sven.gi...@gmail.com> wrote:
> >
> >> additionally i also pulled the following versions and will maintain them
> >>  - phpMp2 0.11.0
> >>  - phpMp+ 0.2.3
> >>
> >
> > Great news to see somebody revive an old MPD client!  Since the
> > project is abandoned, you could continue the original project, without
> > a rename.
> >
> > I cloned your repository, but I was baffled that git downloaded 46 MB
> > of changesets.  You didn't preserve the old change history, but
> > created a whole new repository, and you committed several large
> > tarballs into it, only to remove them with the next commit.
> >
> > Why did you import 4 versions of phpmp?  Which one of these are you
> > going to work on?
> >
> > Why not clone the original git repository, and work on that?  We could
> > give you write access to git.musicpd.org.
> >
> > Oh, and please fix your git configuration:
> >
> >  Author: tswaehn <tswa...@homer.(none)>
> >  Author: root <r...@homer.(none)>
> >
> > Max
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Musicpd-dev-team mailing list
> Musicpd-dev-team@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team
>
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Musicpd-dev-team mailing list
Musicpd-dev-team@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/musicpd-dev-team

Reply via email to