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

Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)

From
Philip Oakley <philipoakley@iee.org>
Date
Mar 17, 2014, 22:39 UTC
Message-ID
<A3D6A8DA9247437B9B4751C5C5B6924C@PhilipOakley>
In-Reply-To
<CALkWK0npxgi2gWQbuYZLn_N0GxgTdPTR8c-yhgCxEV=mM2Zngw@mail.gmail.com>
From: "Ramkumar Ramachandra" <artagnon@gmail.com>
Show 17 quoted lines
> Philip Oakley wrote:
>>> * po/everyday-doc (2014-01-27) 1 commit
>>> - Make 'git help everyday' work
>>>
>>> This may make the said command to emit something, but the source is
>>> not meant to be formatted into a manual pages to begin with, and
>>> also its contents are a bit stale.  It may be a good first step in
>>> the right direction, but needs more work to at least get the
>>> mark-up right before public consumption.
>>
>> I'm not sure what elements you feel need adjustment. At the moment 
>> the
>> markup formats quite reasonably to my eyes, both as an HTML page and 
>> as a
>> man page.
>
> I sent you a small patch fixing some minor markup issues.

Thanks, I'll look through them. There was one part where there was a sub-list which made the numbering look wrong, but it formatted fine.

Show 15 quoted lines
>
>> That said, the (lack of) introduction could do with a paragraph to 
>> introduce
>> the "guide". I have something in draft..
>>
>> I had a thought that it may be worth a slight rearrangement to add a 
>> section
>> covering the setting up of one's remotes, depending whether it was 
>> forked,
>> corporate, or independent, but the lack of resolution on the next
>> {publish/push} topic makes such a re-write awkward at this stage. 
>> (Ram cc'd)
>
> Before attempting to introduce remote.pushdefault and triangular
> workflows, I'd first fix the main issue: stale content.

My priority order was to fix accessibility, then basic format, followed by a nicer intro, and then the "current" content, rather than get hung up on initially word-smithing new content, which could go down a rabbit hole which would leaving the stale content in place. Hopefully the patch will bring out some more clarifications that folks feel are outdated or no longer informative.

>     I'm not sure
> who uses git show-branch or mailx anymore, for instance.

I hadn't even realised mailx was refering to specific program rather than a generic "mail-MUA-X" ;-)

regards
Philip 
Previous: Junio C HamanoNext: Junio C Hamano
Message 14 of 17 in “What's cooking in git.git (Mar 2014, #03; Fri, 14)”
  1. Junio C HamanoMar 14, 2014
  2. Torsten BögershausenMar 15, 2014
  3. Junio C HamanoMar 17, 2014
  4. Max HornMar 19, 2014
  5. Max HornMar 19, 2014
  6. Junio C HamanoMar 19, 2014
  7. Max HornMar 19, 2014
  8. Junio C HamanoMar 19, 2014
  9. Duy NguyenMar 15, 2014
  10. Junio C HamanoMar 17, 2014
  11. Philip OakleyMar 16, 2014
  12. Ramkumar RamachandraMar 16, 2014
  13. Junio C HamanoMar 17, 2014
  14. Philip OakleyMar 17, 2014
  15. Junio C HamanoMar 17, 2014
  16. Philip OakleyMar 18, 2014
  17. Jeff KingMar 18, 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.