www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Riou" <matth...@offthelip.org>
Subject Re: Best Practices so far?
Date Fri, 02 May 2008 16:28:36 GMT
On Fri, May 2, 2008 at 9:16 AM, Henning Schmiedehausen <hps@intermeta.de>
wrote:

> Sorry, I disagree.
>

No need to be sorry :)


>
> man git-svn(1) does not contain any reference to log-window-size.
>
> % rpm -qf /usr/share/man/man1/git-svn.1.gz
> git-svn-1.5.4.1-1.fc8
>

Ah yes, so that's one missing option. Actually I was referring to git man
pages in general, not git-svn or this option specifically. But YMMV as
always.

Cheers,
Matthieu


>
> (as included with Fedora 8)
>
> git-svn also contains no online help (neither --help, nor -h). And while
> I read perl pretty well, thank you, I want to *use* that program, not
> develop or debug it. :-)  I have other fish to fry.
>
>
>        Best regards
>                 Henning
>
> On Fri, 2008-05-02 at 08:51 -0700, Matthieu Riou wrote:
> > On Fri, May 2, 2008 at 3:07 AM, Henning Schmiedehausen <hps@intermeta.de
> >
> > wrote:
> >
> > > BTW, if you want to have fun, try finding documentation for that
> > > parameter. Only then you will realize, how spoiled we are with the
> > > Redbook.
> > >
> > > That is IMHO the biggest obstacle to git: Bad, missing, outdated docs.
> > >
> >
> > Try man, their man pages are really good and up to date. I'm guessing
> it's
> > the reference documentation as they see it. They even include a lot of
> small
> > usage examples. For example:
> >
> > man git-svn
> > man git-rebase
> >
> > Cheers,
> > Matthieu
> >
> >
> > >
> > >        Best regards
> > >                 Henning
> > >
> > >
> > > On Fri, 2008-05-02 at 12:05 +0200, Henning Schmiedehausen wrote:
> > > > Yep. --log-window-size=10000
> > > >
> > > >       Best regards
> > > >               Henning
> > > >
> > > >
> > > > On Fri, 2008-05-02 at 10:33 +0100, Justin Mason wrote:
> > > > > Jukka Zitting writes:
> > > > > > Hi,
> > > > > >
> > > > > > On Fri, May 2, 2008 at 11:22 AM, Davanum Srinivas <
> davanum@gmail.com>
> > > wrote:
> > > > > > > So, what's the learning so far? Example how does one set
up a
> > > git-svn for a
> > > > > > > specific Apache project?
> > > > > >
> > > > > > I've cloned a few smaller projects like this:
> > > > > >
> > > > > >  git svn clone -s http://svn.apache.org/repos/asf/incubator/
> > > <project>
> > > > > >
> > > > > > So far I've avoided doing that with TLPs because of the load
on
> the
> > > > > > svn server, but now that svn.eu.apache.org is in place I'm
> running
> > > the
> > > > > > following:
> > > > > >
> > > > > >  git svn clone -s http://svn.eu.apache.org/repos/asf/jackrabbit
> > > > > >
> > > > > > Note that these clones take quite a while (hours) to create,
but
> > > after
> > > > > > that it's quite easy and fast to keep them up to date with
> latest
> > > > > > changes.
> > > > >
> > > > > This is useful info -- thanks!
> > > > >
> > > > > I noticed on the infra list there was mention of a parameter which
> > > > > restricts how many commits to span in the SVN history; it might be
> > > useful
> > > > > to add that to this "best practices" thread...
> > > > >
> > > > > --j.
> > > --
> > > Henning P. Schmiedehausen  -- hps@intermeta.de | JEE, Linux, Unix
> > > 91054 Buckenhof, Germany   -- +49 9131 506540  | Apache Java Software
> > > Open Source Consulting, Development, Design    |
> > >
> > > INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB
> 7350
> > > Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning
> Schmiedehausen
> > >
> > >  char name_buf[257];           /* max unix filename is 256, right? */
> > >
> > >
> > >
> --
> Henning P. Schmiedehausen  -- hps@intermeta.de | JEE, Linux, Unix
> 91054 Buckenhof, Germany   -- +49 9131 506540  | Apache Java Software
> Open Source Consulting, Development, Design    |
>
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
> Gesellschaftssitz: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
>
>  char name_buf[257];           /* max unix filename is 256, right? */
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message