From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: <git@vger.kernel.org>
Subject: Re: Everday contents
Date: Sun, 03 Aug 2014 10:29:20 -0700 [thread overview]
Message-ID: <xmqqfvhdtrbj.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <35435A61F3C04DC8924B2E2329F9461E@PhilipOakley> (Philip Oakley's message of "Sat, 2 Aug 2014 18:28:58 +0100")
"Philip Oakley" <philipoakley@iee.org> writes:
> From: "Junio C Hamano" <gitster@pobox.com>
> Sent: Friday, July 25, 2014 11:08 PM
> ...
>>
>> | Individual Developer (Participant)[[Individual Developer
>> (Participant)]]
>> | ------------------------------------------------------------------------
>
> ...
>> | $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL
>> <5>
>
> Would I be right that "ALL" can simply be dropped as something from
> back then' (13 Dec 2005 v0.99.9-516-g44db136) that I'm ignorant of?
The answer depends on the reason why you want to drop it from the
example.
That "ALL" is merely a branch name, like "master", etc. I do not
know how jgarzik names his published branches these days, but back
then ALL there was something that contained all the topics he wanted
others to look at. And the description of <5> explains it to be
fetching a "specific branch", so that needs to be reworded if we are
to change the example to "from the default branch of a specific
repository" or something.
> ...
>> | <5> fetch from a specific branch from a specific repository and
>> merge.
Thanks.
next prev parent reply other threads:[~2014-08-03 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 21:44 What's cooking in git.git (Jul 2014, #04; Tue, 22) Junio C Hamano
2014-07-23 6:56 ` Philip Oakley
2014-07-23 18:10 ` Junio C Hamano
2014-07-24 22:37 ` Philip Oakley
2014-07-24 22:45 ` Junio C Hamano
2014-07-25 22:08 ` Junio C Hamano
2014-07-28 22:12 ` Philip Oakley
2014-07-30 17:13 ` Everyday contents (was Re: What's cooking in git.git (Jul 2014, #04; Tue, 22)) Junio C Hamano
2014-08-05 20:26 ` Junio C Hamano
2014-08-05 21:00 ` Philip Oakley
2014-08-02 17:28 ` Everday contents (was part of " Philip Oakley
2014-08-03 17:29 ` Junio C Hamano [this message]
2014-08-03 18:41 ` Everday contents Philip Oakley
2014-08-04 17:00 ` Junio C Hamano
2014-07-23 14:17 ` What's cooking in git.git (Jul 2014, #04; Tue, 22) Karsten Blees
2014-07-23 18:24 ` Junio C Hamano
2014-07-25 12:30 ` Duy Nguyen
2014-07-29 19:43 ` [RFC/PATCH] Windows tests: let $TRASH_DIRECTORY point to native Windows path Karsten Blees
2014-08-27 13:08 ` Duy Nguyen
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=xmqqfvhdtrbj.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.