Re: Jabber, question on push,pull and --tags, and no help but jabber

From: Steffen Daode Nurpmeso <sdaoden@googlemail.com>
Date: Jun 7, 2011, 10:24 UTC
Message-ID: <20110607102444.GA85904@sherwood.local>
In-Reply-To: <4DEDBB56.7000200@drmicha.warpmail.net>

@ Michael J Gruber <git@drmicha.warpmail.net> wrote (2011-06-07 07:47+0200):

> > +	refs under `refs/heads/` be pushed explicitely.
> 
> I don't mind but I don't think it adds clarity.

Yes you're right - it was around midnight and i was tired. That's a stupid change.

> That is implicit in the line before it. In any case: The main problem of
> git-push(1) seems to be that one has to read all the way down (through
> all options) in order to grasp the default case,

In fact i'm lazy, so i'll assume that hardly happens until the first error occurs :).

> so I feel the first paragraph needs to improve.

This morning i've reread tutorial(-2)? and user-manual, which, plus core-tutorial, where the files i've really read :-). And guess what, in neither of these files you will find a single word or even example about this, but the talk is only on branches! everyday.txt and gitworkflows.txt, however, give you

    <13> push the tag out, too.
..
    You need to push the new tag to a public git serve..
    This makes the tag available

Interesting ", too" and "You need to" that is, maybe ;-/. I'll propose for real fewest minor changes in the documentation, so that users get a glance on that fact. I would assume that these few lines would have been enough for me to "get a starter".

Thanks for the responses. (By the way: "an arbitrary SHA-1 expression will do" sounds like it's talking about a cool and flexible software.) -- Ciao, Steffen sdaoden(*)(gmail.com) () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments