[Pkg-phototools-devel] Fixing a commit (log) mistake on openjpeg.git

[Robin Cornelius]

On Jan 29, 2008 11:28 AM, Cyril Brulebois
<cyril.brulebois at enst-bretagne.fr> wrote:

> I'd say it's not that important and you can leave it as is, everyone can
> do something wrong/not the optimal way. :) One way to fix it would be to
> rewrite the branch on alioth, which would be evil for people tracking
> your repository (one can do that with git-filter-branch, which I used to
> rewrite the foo at computer addresses of the git-svn-imported tree into Foo
> <bar at domain>; but that's rewriting, and that's evil on published
> branches).

Ok, I would prefer to leave it rather than rewrite the repository and
if its not bothering anyone too much then this is probably the best
thing to do.


>
> > Whilst i am writing an email. I was going to ask about the way to move
> > forward with openjpeg. I don't mean to sound pushy but would just like
> > to check etiquette. Should I go back to mentors with the updated
> > version and issue a fresh RFS (and I suspect copy this list too) and
> > just see what happens or should i just wait and someone here will move
> > things when they have the free time?
>
> I don't think we ever discussed this, I guess that you could call for an
> RFS here, and once there's no more comment (or if there's none at all),
> just go find your favourite sponsor, or mentors.
>
> I can have a look within the next day, but I won't be able to sponsor
> you in the end.

Ok thanks, if you can provide any feedback this should hopefully
reduce the time spent finding a sponsor etc by having a better quality
package to start with. Then as suggusted I will start with a RFS on
this list.

Many thanks

Robin