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/3] Documentation: refine refspec description
Date: Mon, 26 Jan 2009 00:45:30 +0100 [thread overview]
Message-ID: <1232927133-30377-1-git-send-email-mail@cup.kalibalik.dk> (raw)
These are the remaining parts of my git-push refspec updates.
I recall having a hard time making sense of the existing
documentation, due to a lot of small questions that popped up.
With these patches, I try to reword things to make them clearer.
It is, however, getting to the point where I have looked at this so
much that I can no longer tell whether I am actually improving things.
Thus, this will be my last submission for this particular itch.
Cheers,
Anders.
next reply other threads:[~2009-01-25 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 23:45 Anders Melchiorsen [this message]
2009-01-25 23:45 ` [PATCH 1/3] Documentation: simplify refspec format description Anders Melchiorsen
2009-01-25 23:45 ` [PATCH 2/3] Documentation: more git push examples Anders Melchiorsen
2009-01-25 23:45 ` [PATCH 3/3] Documentation: rework src/dst description in git push Anders Melchiorsen
2009-01-26 6:24 ` [PATCH 1/3] Documentation: simplify refspec format description 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=1232927133-30377-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).