git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anders Melchiorsen <mail@cup.kalibalik.dk>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Anders Melchiorsen <mail@cup.kalibalik.dk>
Subject: [PATCH 0/4] Clarifying the refspec documentation
Date: Sun, 18 Jan 2009 15:36:54 +0100	[thread overview]
Message-ID: <1232289418-25627-1-git-send-email-mail@cup.kalibalik.dk> (raw)

This is a partial resend of some small updates to the git-push
refspec documentation. I have removed the parts of the patch
series that had comments last time, and will rework those later.

Meanwhile, I think that these simple modification do help in
making things more readable. Once you understand the refspec, it
is hard to realize how hard those few paragraphs are to digest.


Anders Melchiorsen (4):
  Documentation: git push repository can also be a remote
  Documentation: remove a redundant elaboration
  Documentation: mention branches rather than heads
  Documentation: avoid using undefined parameters

 Documentation/git-push.txt |   15 ++++++++-------
 1 files changed, 8 insertions(+), 7 deletions(-)

             reply	other threads:[~2009-01-18 14:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-18 14:36 Anders Melchiorsen [this message]
2009-01-18 14:36 ` [PATCH 1/4] Documentation: git push repository can also be a remote Anders Melchiorsen
2009-01-18 14:36   ` [PATCH 2/4] Documentation: remove a redundant elaboration Anders Melchiorsen
2009-01-18 14:36     ` [PATCH 3/4] Documentation: mention branches rather than heads Anders Melchiorsen
2009-01-18 14:36       ` [PATCH 4/4] Documentation: avoid using undefined parameters Anders Melchiorsen
2009-01-19  3:46       ` [PATCH 3/4] Documentation: mention branches rather than heads Junio C Hamano

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=1232289418-25627-1-git-send-email-mail@cup.kalibalik.dk \
    --to=mail@cup.kalibalik.dk \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).