Ludovic Courtès writes:
> Paul Landes <landes@...> writes:
> > Hmmmm, another idea is to create people like you who have been
> > submitting a lot of patches an account on SF and give tracker access.
> > This wouldn't be a commit priv, but would allow you to put your
> > patches directly into SF for tracking. Then you could just paste in
> > tracker IDs or URLs or something.
> As far as I'm concerned, using git-svn to maintain patches locally it
> not a problem, as far as I don't end up having a local branch that
> diverges too much from trunk because patches haven't been reviewed for
> inclusion---but so far you've been very fast at reviewing!
> I actually even prefer git-svn + email over SF's web interface.
I've not used it enough to get a good sense. The reporting features
seem nice, but for us that's less useful. Mail is fine as well. The
only thing I care about is really ease of applying the patch to look
at it and test it. The less I have to munge paths the faster it gets
We need to standardize on patches and it could be your way. If so,
I'd apply the patches the same every time. However, most submit in a
way that doesn't require path stripping and have been. I think the
overall effort is reduced if you submit patches like others.