git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Daode Nurpmeso <sdaoden@googlemail.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: Jabber, question on push,pull and --tags, and no help but jabber
Date: Tue, 7 Jun 2011 12:24:44 +0200	[thread overview]
Message-ID: <20110607102444.GA85904@sherwood.local> (raw)
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

  reply	other threads:[~2011-06-07 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 13:02 Jabber, question on push,pull and --tags, and no help but jabber Steffen Daode Nurpmeso
2011-06-06 14:31 ` Michael J Gruber
2011-06-06 15:21   ` Felipe Contreras
2011-06-06 21:46   ` Steffen Daode Nurpmeso
2011-06-07  5:47     ` Michael J Gruber
2011-06-07 10:24       ` Steffen Daode Nurpmeso [this message]
     [not found] ` <9215090.63086.1307370716794.JavaMail.trustmail@mail1.terreactive.ch>
2011-06-06 15:34   ` Victor Engmark
2011-06-06 17:58     ` Junio C Hamano
2011-06-07 10:48 ` [PATCH] Notes that tags need to pushed explicitely Steffen Daode Nurpmeso
2011-06-07 14:12   ` Junio C Hamano
2011-06-07 15:33     ` [PATCH] Remarks that tags need to be pushed explicitly Steffen Daode Nurpmeso
2011-06-10 20:39     ` [PATCH v2] " Steffen Daode Nurpmeso
2011-06-10 21:24       ` Junio C Hamano
2011-06-11 17:20         ` Steffen Daode Nurpmeso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110607102444.GA85904@sherwood.local \
    --to=sdaoden@googlemail.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).