Carl Worth <cworth@xxxxxxxxxx> writes:
> It's more that I want a single way to talk about some branch I've just
> published, (necessarily both a url and a branch), and I assume an
> audience with a wide range of git experience, (from none to lots).
Why would you want to add another syntax that can talk about
only one branch? It shows that you care only about talking
about single branch, making things harder for other people who
might want to talk about two branches or more.
I would agree with you that if you are talking to total git
newbie, you cannot get away with message like [3] in your
original and you would need some instructions you added in your
example [2]. But I suspect that is true for any new system. If
somebody has never seen cvs and your project is hosted at cvs,
and if you want to be really helpful, I think you have to tell
"cvs -d :pserver:... co cworth-project" somewhere in your
message.
But that does not have to be in the main part of the
announcement, like this (this is your [2]):
I've just written some very fancy feature for our cool project
which you can see in gitweb at <gitweburl>. To track this
branch, do "git remote add cworth <url>; git checkout --track
-b <branch> cworth/<branch>" if you already have some clone of
our project. Otherwise do "git clone <url>; git checkout
--track -b <branch>". Please try it out and give me feedback.
You can say instead:
I've just written some very fancy feature for our cool project
which is available in the <branch> branch at <url>. Please try
it out and give me feedback. [*1*]
[Footnote]
*1* If you have never used git, here are the ways to get at
the cool project ...
<<< instruction here >>>
If you have been tracking the upstream of the cool
project, alternatively you can do this to get to my
fancy feature as a new branch in your repository ...
<<< instruction here >>>
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html