git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Everday contents

From
Philip Oakley <philipoakley@iee.org>
Date
Aug 3, 2014, 18:41 UTC
Message-ID
<E675F06626AA430EB89D68FF67734824@PhilipOakley>
In-Reply-To
<xmqqfvhdtrbj.fsf@gitster.dls.corp.google.com>
From: "Junio C Hamano" <gitster@pobox.com>
Show 21 quoted lines
> "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.

That was the bit I was missing. I had it in my head that it was possibly some historic option as it was in caps.

Show 5 quoted lines
>  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

I eventually went with using a lower case 'dev' as a nominal branch name, and also named it in the updated <5>. However I hadn't actually checked if the repos is still active.

Show 7 quoted lines
> 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.
Philip 
Previous: Junio C HamanoNext: Junio C Hamano
Message 13 of 19 in “What's cooking in git.git (Jul 2014, #04; Tue, 22)”
  1. Junio C HamanoJul 22, 2014
  2. Philip OakleyJul 23, 2014
  3. Junio C HamanoJul 23, 2014
  4. Philip OakleyJul 24, 2014
  5. Junio C HamanoJul 24, 2014
  6. Junio C HamanoJul 25, 2014
  7. Philip OakleyJul 28, 2014
  8. Everyday contents (was Re: What's cooking in git.git (Jul 2014, #04; Tue, 22))Junio C Hamano, Jul 30, 2014
  9. Junio C HamanoAug 5, 2014
  10. Philip OakleyAug 5, 2014
  11. Everday contents (was part of Re: What's cooking in git.git (Jul 2014, #04; Tue, 22))Philip Oakley, Aug 2, 2014
  12. Junio C HamanoAug 3, 2014
  13. Philip OakleyAug 3, 2014
  14. Junio C HamanoAug 4, 2014
  15. Karsten BleesJul 23, 2014
  16. Junio C HamanoJul 23, 2014
  17. Duy NguyenJul 25, 2014
  18. Windows tests: let $TRASH_DIRECTORY point to native Windows pathKarsten Blees, Jul 29, 2014
  19. Duy NguyenAug 27, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.